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

Beyond readOnlyHint and openWorldHint, the description discloses that the tool reads an existing receipt, performs a metadata-only check, does not create anything, and refuses under specified conditions. That is useful behavioral context, though it says nothing about permissions, rate limits, or the exact response shape.

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?

The description is short and front-loads the gating condition before the behavioral caveat. However, telegraphic phrasing such as 'cite slug@height' and semicolon-separated fragments make it more cryptic than efficient.

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 verify-style tool with no output schema and an undocumented required hash parameter, the definition should explain the input meaning and expected result. It only sketches the metadata-check behavior and refusal condition, leaving the actual return values and hash semantics unclear.

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 for the single required hash parameter is 0%, so the description must compensate, but it never explains what the hash represents or how it relates to slug@height. The parameter is therefore left almost entirely to the schema's name and pattern.

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 identifies a specific operation: reading an existing receipt and performing a metadata check rather than local OTS cryptographic verification. It also explicitly says there is no creation, which helps distinguish it from a stamping sibling, though it never plainly states that the input hash is what is being verified.

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?

It gives a clear conditional gate: cite slug@height only when status is confirmed and proofFile exists, otherwise refuse. It also supplies exclusions by saying this reads an existing receipt and is not local OTS cryptographic verification, but it does not name which sibling tool to use when creation or cryptographic verification is actually needed.

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