pending_alerts

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

readOnlyHint=true already declares this is a safe read, and the '[READ]' prefix merely restates that. The description adds some value by signaling results are organized 'by severity' and that omitting target falls back to a default, but discloses nothing about empty results, pagination, or how pending state is determined.

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?

Very short and front-loaded: the scope sentence comes first, followed by a compact Args block. The only waste is the '[READ]' prefix, which duplicates readOnlyHint and earns no new information.

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 single-optional-parameter read tool with annotations covering the safety profile and no output schema, the definition supplies what an agent needs: what is returned (pending, non-firing alerts), how they are arranged (by severity), and how to pick a target. Only minor gaps remain around empty-result handling.

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% and the single 'target' parameter has no schema description at all, so the description carries the burden — and it does, explaining the parameter is a Prometheus target name from config and that omission selects the default. It stops short of describing valid naming formats or error behavior for an unknown target.

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 names a specific resource ('Prometheus rule alerts') and pins down the exact state with the parenthetical 'pending (not-yet-firing)', which effectively separates it from the sibling firing_alerts. It doesn't explicitly name that sibling or state a verb, falling just short of full sibling routing.

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?

Usage is implied by the 'pending (not-yet-firing)' qualifier, so an agent can infer this is the pre-firing counterpart to firing_alerts, but there is no explicit when-to-use/when-not-to-use guidance or named alternative. The only direct instruction is 'omit for the default' on the target.

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