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

Discloses auth requirements, fallback behavior (returns instructions without key), and output fields. Annotations already declare readOnlyHint and idempotentHint, so description adds value by explaining the key requirement and response format.

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?

Three concise sentences, each serving a distinct purpose: purpose, auth requirement, and read-only guarantee. No filler.

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 one optional param, no output schema, and strong annotations, the description covers all key behavioral aspects including missing-key behavior, output summary, and safety. Fully complete for this tool's complexity.

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 covers the single parameter fully (description already explains server-side filter). Description does not add further details, so baseline 3 is appropriate.

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 it lists the calling company's own tracked documents with expiry details, urgency levels, and recommended actions. It distinguishes from siblings like avizo_docs by emphasizing 'own' and specifying the data fields.

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?

Provides explicit prerequisites (API key), behavior without a key, and confirms read-only nature. Does not explicitly compare to siblings but the purpose scoping implies when to use.

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