Prom Range

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. It indicates a read-oriented range query, but does not state that it is non-mutating, how the response is shaped, whether there are limitations on time ranges, or what happens on invalid parameters.

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 short with no filler, and the key idea ('range query over a period') is front-loaded. It is a fragment rather than a complete sentence, but it is efficient for what it attempts to convey.

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?

Given the generic schema, lack of annotations, and the conceptual complexity of a Prometheus range query, the description is not sufficient for an agent to call the tool correctly. It identifies the domain but omits essential input construction details; the output schema may help with responses, but not with building the request.

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?

The schema offers only a generic 'params' object with additionalProperties true and no documentation, and schema description coverage is 0%. The description adds only 'period' as a vague hint and does not specify the necessary query expression, start/end times, or step/interval fields an agent would need to construct valid parameters.

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 that this is a range query over a time period, for charts/history, which is a clear resource and operation. It distinguishes itself from sibling prom_query by focusing on range/period semantics, though it lacks an explicit verb like 'returns' or 'fetches'.

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 phrase 'за период (графики/история)' gives clear context: use this tool for time-range data, charts, or historical queries. It does not explicitly name alternatives like prom_query for instant queries, but the period/history framing makes the intended use reasonably clear.

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