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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description doesn't need to restate those. It adds useful behavioral context by calling the receipt 'permanent protocol proof,' implying immutability, and by explaining what event the receipt certifies. No contradiction with annotations.

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 front-loaded sentence with no wasted words; it states the operation, the object, and the key semantic constraint in one breath.

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-only tool with an output schema and safety annotations, the description is largely sufficient. It misses only explicit sibling differentiation and a note about not-found behavior, but neither prevents a competent agent from calling the tool correctly.

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?

With 0% schema description coverage, the description should compensate by explaining reach_receipt_id, but it never mentions the parameter or how to obtain it. The pattern in the schema provides format, and the description only indirectly indicates what the ID refers to, so parameter semantics are under-specified.

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 uses a specific verb 'Read' and a specific resource: permanent protocol proof of a relay acceptance. This clearly identifies the tool as a receipt-verification read operation and distinguishes it from the generic get_receipt sibling by describing the reach-specific event it proves.

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 gives a clear context — use this when you need to read a permanent proof of a reach/relay acceptance. However, it never explicitly states when not to use it or names get_receipt as the alternative for other receipt types, leaving some sibling routing to inference.

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