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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by disclosing the auth requirement ("Requires the organization API key"), the signing algorithms (Ed25519 and ML-DSA-87), and the fact that the package is self-contained and verifiable offline. It does not mention rate limits, size limits, or whether export is logged/notified, keeping it short of a 5.

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 dense sentences with zero filler: the verb and resource are front-loaded, the enumerated bundle contents follow, and the second sentence carries the verification path and auth prerequisite. Every clause earns its place.

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 single-parameter, non-destructive read tool with annotations covering the safety profile and no output schema to explain, the description supplies the missing pieces: what the artifact contains, how to verify it offline, and that an org API key is required. Only the origin/selection of stream_id is left 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?

Only one parameter (stream_id) with 100% schema description coverage, so the schema already documents it. The description adds nothing about where to obtain a stream_id (e.g. ledger_list_streams) or what a stream represents, so the baseline 3 applies.

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 ("Export") and a precisely enumerated resource: every entry, hash chain, RFC 9162 inclusion proof, signed tree head, on-chain checkpoint and keys. This level of content specification clearly distinguishes it from siblings such as ledger_report_pdf, ledger_compliance_report and ledger_inclusion_proof.

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?

Gives a clear use context ("for auditors, courts or air-gapped systems") and points to the offline verification path via verify_bundle.py. It does not, however, state when an agent should prefer this over sibling artifacts like ledger_report_pdf or ledger_compliance_report, so routing among near-neighbors is left to inference.

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