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

With no annotations, the description carries the full burden of behavioral disclosure. It thoroughly explains the computation method (pretty-printed JSON, 2-space indent, key order preserved), the input variants (wrapped object or bare draft), and the limitations of what the verification proves. However, it does not mention what happens on digest mismatch or whether the tool has side effects, which would make it fully transparent.

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 two sentences and front-loads the primary action in the first sentence. The second sentence is dense but packs essential nuance about the verification scope and serialization format. Every sentence earns its place, though the long second sentence could be slightly restructured for easier scanning.

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?

The description lacks any mention of the tool's output or return value. Since there is no output schema, the description should indicate what the tool returns (e.g., boolean, match/mismatch, or error details). For a verification tool, the result is the core purpose, so omitting it leaves a significant gap. The input handling is well covered, but the output is absent.

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?

The schema already documents the parameter with 100% coverage, but the description adds valuable semantic detail: 'Accepts the wrapped {mandate_draft, digest} file or a bare draft.' This clarifies the accepted shapes beyond the schema's anyOf object/string, making it easier for the agent to construct valid input.

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 clearly states the tool's function: 'Recomputes the SHA-256 digest... and compares it to the digest embedded in the file.' It goes beyond a simple verb+resource by explaining exactly what the verification establishes and what it does not, effectively distinguishing it from sibling tools related to ceremonies and schema.

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 description provides clear context for when to use the tool by explicitly stating its scope: 'Establishes that the file is internally consistent... NOT that it was minted, and not that capital.new has ever seen it.' This exclusion of provenance claims is a form of when-not-to-use guidance, though it does not name alternative tools directly.

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