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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose what the tool actually does (e.g., sets a pin, checks pinnability), nor does it mention side effects, permissions, reversibility, or return behavior. The single cryptic condition is insufficient.

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 a single fragmented phrase. While short, it is under-specified rather than concise; it does not front-load a clear purpose or provide structure for an agent to parse.

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 the nested object parameter, absence of output schema, and no annotations, the description is far too incomplete. It does not convey what the tool returns, how it behaves, or what the required receipt object represents, making correct invocation unlikely.

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 the one parameter is a nested object. The description does not explain what the 'receipt' object should contain or what 'verifying CANONICAL' means in terms of parameter structure, leaving the schema entirely undocumented.

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 'PINNABLE only for a verifying CANONICAL receipt' does not state a clear action or resource. It hints at pinning and canonical receipts, but an agent cannot confidently tell what the tool does or how it differs from get_receipt or verify_candidate.

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 phrase 'only for a verifying CANONICAL receipt' implies a precondition, but it does not explain when to use this tool, when not to, or how it relates to the sibling tools get_receipt and verify_candidate. No explicit alternatives are mentioned.

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