Prom Query

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'query'. It does not mention that the operation is read-only, what the response contains, or any timeout/pagination behavior, so an agent has little behavioral context.

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 text is extremely short and free of filler, which is structurally concise. However, it is under-specified rather than efficient, and the lack of any parameter or usage details means the brevity does not earn its place.

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 a tool whose only parameter is an opaque object, the description and schema together do not explain how to invoke it. The presence of an output schema reduces the need to document return values, but the input side remains essential and is left undocumented.

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 coverage is 0% and the sole 'params' object is unconstrained. The description does not say what keys to pass, such as the PromQL expression or evaluation time, so the agent cannot construct a valid invocation from the definition.

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 an instant PromQL query ('Instant query (PromQL) к Prometheus'), giving a specific action and target resource. It partially distinguishes from prom_range by using 'instant', although it does not name sibling alternatives explicitly.

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?

No guidance is provided on when to use prom_query versus prom_range, prom_alerts, or prom_targets. The word 'instant' implies but never states that this should be chosen for point-in-time queries rather than time-range queries.

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