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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that results are scoped to the account and that pagination is supported, which is modest but real extra context. It omits pagination mechanics, result limits, and what "recent" actually means.

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?

Two short sentences, front-loaded with the core purpose. No filler. The second sentence is somewhat vague ("pagination query parameters") but still earns its place by hinting at accepted input.

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 and a catch-all query object, the description carries the burden of explaining what inputs are usable and what comes back. It mentions pagination but not the parameter names, result shape, or default limits, leaving meaningful gaps for an agent trying to page through receipts.

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 nominally 100%, but the schema only defines an open-ended query object with anyOf string/number/boolean, which names no concrete parameters. The description compensates slightly by saying the query supports pagination, but it never names the pagination keys or their formats, so an agent still has to guess. Baseline 3 for high coverage with minimal added value.

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 states a specific verb and resource: "List recent verification receipts issued to the account." An agent knows exactly what it returns without opening the schema. It does not, however, differentiate itself from verification-adjacent siblings like affix_verify or affix_aggregate_verify, so it falls short of a 5.

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?

There is no guidance on when to call this versus alternatives such as affix_verify or affix_verify_reason_codes, nor any stated prerequisites. Usage is only implied by the word "List."

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