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

Annotations already cover the safety profile (readOnlyHint=true) and the closed-corpus nature (openWorldHint=false); the description usefully reinforces this by stating the list is a fixed, verified set of 83 documents and that results carry a document_id for chaining. It does not discuss pagination behavior or what happens on zero matches, so it stops short of a 5.

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 tightly written sentence that front-loads the operation and corpus, then gives the matching keys, examples, and return shape. No filler or redundancy.

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?

With no output schema, the description correctly discloses the return shape (matching documents plus document_id). It leaves minor gaps: no explicit pointer to get_photo_requirements for full requirements, and no note on behavior when nothing matches.

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 description coverage is 100%, so both parameters are already documented, including examples for query and the default/max for limit. The description's 'by country, document or form name' largely restates the schema, adding little beyond confirming query is free-text, 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?

States a specific verb and resource ('Search ... list of 83 passport and visa photo documents') plus exact lookup keys (country, document, form name) and concrete example queries. The detail that it 'returns matching documents with their document_id' signals search-then-fetch semantics, which distinguishes it from an id-based sibling like get_photo_requirements.

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?

Gives clear context for when to call it (free-text lookup by country, document, or form name) and rich examples ('US visa', 'DS-160', 'Schengen', 'India OCI', 'Dubai'). It stops short of explicitly naming alternatives or stating when not to use it, e.g. fetching details by a known document_id.

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