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

With no annotations, the description carries the full burden. It does disclose the critical side-effect profile — nonce is not consumed and nothing is settled — which is genuinely valuable. However, it omits auth/permission requirements, error behavior, and what a failed verification means operationally.

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 with the resource stated first and the behavioral caveat front-loaded rather than buried. It borders on terse for a security-sensitive tool, but no sentence is wasted.

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 tool with no annotations, no output schema, and a nested undocumented parameter, the description covers the safety profile but not the return semantics. An agent cannot learn from it what 'verification' yields (boolean, reason codes, decoded fields), which is a real gap for a verification tool.

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?

The single 'receipt' parameter is an undocumented nested object at 0% schema description coverage, and the description adds no field-level meaning (what a receipt envelope must contain, required fields, format). The word 'envelope' hints at structure but supplies nothing actionable.

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 ('verify_receipt' → 'Receipt envelope inspection') and enumerates the checks performed (signature/expiry/channel). It does not explicitly differentiate itself from siblings like channel_verdict or grounded_verification, but the scope is unambiguous.

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 explicit when-to-use or when-not guidance relative to the sibling tools. The parenthetical 'does not consume the nonce, settles nothing' implies the intended usage context (a non-mutating pre-check), but the agent must infer that this is the lightweight inspection step versus a full settlement flow.

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