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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add meaningful behavior beyond the name: the exclusion of received documents and the priority ordering (expired/overdue first, then by days remaining). However, it does not mention return format, pagination, or any potential error cases, so it is not fully transparent.

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 a single, well-structured sentence that front-loads the primary verb and resource, then adds a concise ordering rule. Every word contributes to understanding, with no fluff or repetition.

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 tool's low complexity (zero params, no output schema, no annotations), the description covers the core behavior and ordering. It does not specify the exact output shape, but the tool name and verb make the list semantics obvious. The missing details are not critical for a simple list operation.

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 has zero parameters, so there is nothing to explain. Per the rubric, zero params earns a baseline of 4. The description does not need to add parameter semantics because none exist.

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: 'List every vendor document that is still missing (not yet received)' with a specific ordering rule ('most critical first — expired/overdue at the top, then by days remaining'). This distinguishes it from sibling tools like search_vendor_docs and get_expiring_docs.

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 provides clear context for when to use the tool: whenever the user needs to see all missing vendor documents. It does not explicitly mention alternatives, but the purpose and ordering make the use case evident. No exclusions are stated, but the specificity of 'every vendor document ... still missing' implies it is the go-to for listing missing items.

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