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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, yet the description adds substantive behavior: Ed25519 signing when a runtime key exists, embedded hash chain and Merkle proof, and no on-chain write. It also discloses a non-obvious input constraint (inputs must be public and non-personal), which is real value beyond the structured fields.

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?

Front-loaded with the use case, then formats, then signing/proof semantics, then constraints — a sensible priority order with no filler sentences. The final clause packs several facts into one semicolon-joined line, which is dense but not wasteful.

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 two-parameter, no-output-schema tool with full schema coverage, the description covers purpose, format semantics, cryptographic behavior, and input constraints. The only real gap is what the exported artifact actually looks like, which the absence of an output schema leaves unstated.

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 100%, so the baseline is 3, but the description enriches the enum with meaning the schema lacks: x402 is "attestation style," erc8004 is a "validation-response shape," and vc is "W3C-VC-like JSON-LD." This helps an agent choose a format rather than guess from bare tokens.

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 gives a specific verb (export/re-render) and resource (a GAIP receipt) and states the operative dimension: converting an existing receipt into a different serialization (x402, erc8004, vc). This clearly separates it from verify_gaip_receipt and gaip_check_sar_receipt, though it never names those siblings explicitly.

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?

"Use this when you need a GAIP receipt in another format" supplies a concrete trigger condition, and the format list makes the selection criteria clear. It stops short of naming alternatives or stating when NOT to use it (e.g., to verify rather than re-render a receipt), which keeps it below a 5.

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