list_pending_pool_requests

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

The description mentions the HTTP method (GET) indicating a read operation, and details pagination via limit and page_token. However, it does not disclose authorization requirements beyond a brief note on repository-scoped keys, nor does it specify rate limits or response structure, which is important given the absence of annotations.

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 very concise: one line for purpose and endpoint, followed by parameter details in a clear list format. No unnecessary words, all sentences add value.

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 presence of an output schema (not shown), the description adequately covers the tool's purpose and parameters. It does not explain return values, but the output schema likely handles that. Overall, it provides sufficient context for an agent to use the tool effectively.

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?

Despite 0% schema description coverage, the description provides meaningful explanations for all three parameters: limit (range and default), page_token (pagination cursor), and repository (optional but required for repo-scoped keys). This fully compensates for the missing schema descriptions.

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 clearly states 'List unassigned pool requests' and includes the HTTP endpoint, which identifies the specific resource. It distinguishes from sibling list tools by specifying 'pending requests' as opposed to other resources like workers or agents.

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 description does not provide any guidance on when to use this tool versus alternatives. It lacks context such as prerequisites, scope of results, or scenarios where other list tools would be more appropriate.

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