Prometheus: Request

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses that only GET is sent, that the response is the raw unshaped data field, that output is truncated at max_chars, and that it can return megabytes. These are exactly the behavioral traits an agent needs for an open-world escape-hatch tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the escape-hatch purpose, followed by examples, scope, safety, and truncation caveats. Every sentence contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-world raw-API tool with a rich schema, the description covers purpose, alternatives, safety, and truncation well. It does not mention error-envelope or non-2xx behavior, which is a minor remaining gap for an arbitrary-endpoint tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with path pattern, params repetition semantics, and max_chars range already documented in the schema. The description reinforces max_chars truncation but does not add new parameter meaning beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: GET any /api/v1 endpoint not covered by the named tools. It explicitly distinguishes itself from siblings by positioning itself as the escape hatch and naming examples of endpoints it handles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('other tools do not wrap') and when-not-to-use guidance ('Prefer the named tools'), naming the alternative category directly. An agent can decide between this and the specific Prometheus tools without inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.