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

No annotations are provided, so the description carries the full disclosure burden. It hints that verification is against a registry, but says nothing about permissions, failure modes, whether verification is read-only, or what a successful/failed result looks like.

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 efficient sentence with no waste, but the terseness comes at the cost of under-specification rather than deliberate brevity – there is essentially nothing front-loaded beyond the basic act.

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?

Given three parameters with nested objects, no annotations, and no output schema, the description is far too thin. An agent cannot know what to pass in task_spec or deliverable_hash, nor what the tool returns, making correct invocation mostly guesswork.

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 three parameters, including two nested objects (receipt, task_spec). The description references only the receipt in passing and adds no meaning about task_spec (presumably a cross-check) or deliverable_hash (presumably the expected hash), so it fails to compensate for the schema gap.

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) and resource (burn receipt) plus a mechanism (the persistent registry), which distinguishes it from siblings like burn_mint and burn_run. However, 'verify' is ambiguous – it doesn't say whether it checks authenticity, existence, signature, or hash match, so the agent cannot reason precisely about what the operation confirms.

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 indication of when this tool should be used versus alternatives such as burn_gate or burn_mint, and no mention of prerequisites (e.g., that a burn must exist first). The agent is left to infer usage purely from the name.

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