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

Annotations already declare readOnlyHint and openWorldHint, and the description adds non-obvious context: it requires no auth token, mirrors GET /api/proofs, and is disabled when the feature check is off. It stops short of describing the response shape or pagination.

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 short clauses with no filler, and the subject (public certification list for a handle) is front-loaded. The REST-endpoint equivalence is compact and useful for agents that know the API.

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?

For a one-parameter read there is no output schema and no return description, so an agent cannot know whether it receives certifications, counts, or booleans. Auth and availability are covered, but the response contract is left implicit.

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 coverage is 100% ('Traveler handle'), so the schema already fully documents the single parameter. 'For a handle' adds no format, scope, or validation detail beyond it; the baseline 3 applies.

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+resource: a public certification list scoped to a handle. It is clearer than a tautology, but it never names or distinguishes itself from siblings like verify_certification or request_certification, so an agent must infer the boundary.

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?

'No token' and 'Not available when that check is off' give real usage context, including an explicit unavailability condition. It never states when to prefer this over verify_certification or recent_postcards, so alternatives remain unaddressed.

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