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

Adds meaningful behavioral context beyond annotations: it discloses the verification checks performed and the important limitation that no live chain canonicality check occurs. However, it does not describe the return value or failure modes, which matters because no output schema is present.

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 tightly written sentences with the core verification scope front-loaded and the limitation stated second. There is no redundant or filler text.

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 tool with a nested object parameter, no schema descriptions, and no output schema, the description leaves key invocation details unknown: the document shape, fingerprint format, and what verification result is returned. It gives enough to understand intent but not enough to call confidently.

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 coverage is 0% and neither parameter is named or described. The phrases 'signed payload' and 'pinned identity' loosely hint at the document and trusted_key_fingerprint parameters, but provide no format, type, or requiredness guidance.

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 specific resources: canonical signed payload, pinned identity, expiry, and source age. It differentiates itself from a live chain canonicality check, though it does not name sibling verification tools such as verify_attestation or verify_quantitative_context.

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?

Provides clear usage context by describing independent verification and an explicit exclusion: 'No live chain canonicality check.' It stops short of naming alternatives for live-chain checks or pointing to sibling tools for related operations.

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