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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavior beyond that: the deterministic SHA-256/canonical-JSON algorithm, the Merkle proof fold, and the comparison target (published daily root), which explains why the call may reach outside the local context. It stops short of noting what happens on mismatch or whether the published root must be fetched.

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 dense sentences with zero filler; the verification mechanism comes first and the input alternatives last. Every clause carries information an agent needs.

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?

There is no output schema, so the description must carry the return contract, and it does not say whether the tool returns a boolean, a validity object, or the expected vs. actual root. For a cryptographic verification tool with an undocumented nested input, this leaves the agent guessing about results and edge cases.

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 0% for both parameters, so the description is the only source — and it does convey the key semantic that 'hash' and 'receipt' are alternative inputs for the same verification. However, it does not clarify that effectively one of the two must be supplied, nor what fields of the nested receipt object are used in the canonical JSON hash.

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 (verify/re-hash) and resource (a receipt) plus the exact mechanism: canonical JSON SHA-256 re-hash, Merkle proof fold, comparison against the published daily root. This is clearly distinguishable from sibling read tools like list_receipts, which merely enumerate receipts rather than cryptographically validating one.

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 parameter-level usage ("Pass the receipt object or its hash") but no guidance on when to prefer this over list_receipts or what happens if using this without a published root. Usage is implied by the verification workflow rather than stated with prerequisites or exclusions.

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