List Applications Pending Review

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds valuable behavioral details: it filters by specific statuses and does not include reviewed applications. It also mentions the sorting order of results. No contradiction found.

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 well-structured and concise, with clear paragraphs for purpose, usage, arguments, and examples. Every sentence adds value, not redundant. Front-loaded with critical 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?

Despite no output schema, the description accurately summarizes the return format. Given the tool's moderate complexity and comprehensive annotations, the description is complete and appropriate. It also covers all parameters and usage patterns.

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 input schema already covers both parameters with descriptions. The description adds behavioral meaning, such as 'unassigned_only' showing applications nobody owns and the filtering effect of 'assigned_reviewer'. Schema coverage is 100%, so description complements rather than repeats.

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 the tool's purpose: listing applications pending a decision with specific review_status values. It distinguishes from siblings by focusing on pending items and explicitly excluding reviewed ones.

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?

It provides clear guidance on when to use this tool (to answer 'what's stuck in the queue') and what it excludes. It also gives behavioral examples for using filters. Although it doesn't state when to use alternatives, the context is explicit and sufficient.

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