list_pending_requests

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a useful filter definition ('deferred requests that have not been processed yet'), but says nothing about ordering, result size, or freshness of the pending set.

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?

A single compact sentence with the scope qualifier front-loaded and no wasted words. It is appropriately sized, though the term 'deferred' is slightly less obvious than 'pending' and goes unexplained.

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 no-parameter read tool with annotations carrying the safety profile and an output schema describing return values, the description is nearly sufficient. The one remaining gap is disambiguation from list_requests, which the agent cannot resolve from the description.

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 tool takes zero parameters, so description-side parameter guidance is not needed. Baseline for a no-parameter tool is 4; the schema fully documents the empty argument object.

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 clear verb (List) and resource (deferred/unprocessed requests), so an agent knows exactly what is returned. However, it does not distinguish this from the sibling list_requests, leaving ambiguity about which listing tool applies.

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 guidance on when to use this tool versus the nearby list_requests sibling, nor any stated preconditions. The agent must infer the difference from wording alone.

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