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

With no annotations, the description does real work by disclosing the output facets (hash match, issuer, anchor state enum values, chain/tx/proof bundle, verify_recipe) and the typed NOT_FOUND error. It still omits whether this is a read-only operation, any auth/permission requirements, and how the two parameters interact.

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?

Front-loaded with the verb and tightly packed, no filler sentences. The single colon-delimited run-on is dense but each listed item (anchor state, proof bundle, verify_recipe) adds information.

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?

No output schema exists, so the description justifiably enumerates return fields, which it does competently. But the critical invocation ambiguity — two optional params, a nested `receipt` object with zero semantics, and no required field — is unresolved, so an agent cannot confidently call it.

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% and both parameters are optional with no required field. The description implies receipt_hash is a hash to verify, but the nested `receipt` object is never explained — what it should contain, or when to pass it instead of/alongside receipt_hash — leaving invocation ambiguous.

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?

Specific verb+resource ("Verify a Herald receipt hash") plus an enumerated statement of what the verification returns. It does not distinguish itself from siblings like trust_get_validation_record, but the resource is distinctive enough that confusion is unlikely.

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 when-to-use / when-not-to-use guidance and no mention of alternatives or prerequisites. The only routing signal is the error case ("Unknown hash returns typed NOT_FOUND"), which tells an agent what happens, not whether this is the right tool.

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