query_prometheus_range

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

There are no annotations, so the description carries the full burden for behavioral disclosure. 'Execute a PromQL range query' implies a read-only operation, and the time-format hints add some context. Still, it does not explicitly confirm read-only behavior, mention result size or limits, or describe what happens with an invalid expression. It is minimally sufficient for a query tool but not rich.

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 extremely concise and front-loaded: the action comes first, followed by only the most essential parameter format guidance. Every word earns its place, and there is no filler or repetition of schema titles.

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?

With an output schema present and moderate tool complexity, the description covers the core temporal parameters and leaves step format clear. However, it omits any guidance on the expr parameter or the optional cluster parameter, and it does not differentiate from the instant-query sibling. It is adequate but has clear gaps that an agent may need to resolve.

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 0%, so the description must compensate. It adds meaningful semantics for start/end (ISO8601 or Unix timestamp) and step (e.g. '5m'), which the schema does not provide. However, it leaves expr and cluster undocumented, so the compensation is incomplete for a 5-parameter tool.

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: 'Execute a PromQL range query.' The word 'range' distinguishes it from the sibling query_prometheus (presumably an instant query), and the mention of start/end/step clarifies the temporal nature. An agent can understand what the tool does without opening the schema.

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?

The description implies when to use the tool by saying 'range query' and gives formatting hints for start/end and step. However, it does not explicitly compare against query_prometheus or list_prometheus_rules, and it provides no exclusions or conditions for when this tool should be preferred.

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