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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by disclosing the ownership constraint (only your own request) and the identity/auth requirement. It does not say what happens when the request is unknown or still pending, which would be the remaining useful disclosure.

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?

Two short sentences, front-loaded with the action and scope, and no filler. Every clause carries information the agent can act on.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The gap is operational: nothing tells the agent when in the request lifecycle to call this tool or how to interpret an empty candidate-match result, which matters for a status-checking primitive.

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% for the single request_id parameter, so the description must compensate; it adds that the id refers to a request scoped to the same caller identity, which is meaningful. It still gives no format or length hints and does not clarify whether it accepts ids from other callers' submissions.

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?

States a concrete verb and resource: reads a queued request plus its candidate matches, scoped to the caller. An agent can tell it is a read-side lookup tool, though the description never names the sibling that creates such requests (request_promotion) or otherwise differentiates itself from siblings in text.

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?

There is no explicit when-to-use guidance, no mention of polling after request_promotion, and no alternatives or exclusions. 'Requires the same caller identity' is a precondition, not usage guidance, so an agent must infer the workflow from context alone.

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