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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds useful non-annotation context (cost, no API key required, which chain the anchor lives on, and the mainnet caveat). One mild tension: openWorldHint=false while the description says it 'checks the anchor on chain (Base)', which implies an external network lookup — worth noting though not a hard contradiction for a read-only vendor-infrastructure verification. It does not describe what a failure verdict looks like.

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?

One compact sentence front-loads the purpose, then lists the three sub-checks and ends with the cost/auth caveat. No redundant restatement of the title or name, and every clause carries distinct information.

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 covers the 'what' and the operational constraints well, but with no output schema the agent gets no sense of the return shape — whether a plain verified/not-verified flag, per-stage results (hash, issuer, anchor), or failure reasons. For a verification tool whose entire value is the verdict, that is a meaningful gap.

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 100% and the single parameter is documented as 'the report object exactly as received from ledger_compliance_report', which already supplies the key guidance. The description adds no further insight into the report object's fields or how mismatches are treated, so it sits at the schema-covered baseline.

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?

Uses a specific verb ('Check that ... is unaltered') and enumerates the three concrete operations performed: hash recomputation, issuer confirmation, and on-chain anchor check. The resource and its provenance (a report from Privi Ledger) are clear. It stops short of naming the closest sibling candidates (ledger_report_pdf, ledger_check_receipt), so differentiation is left to inference.

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 statement that the tool is 'Free; no key needed' plus the hash/issuer/anchor framing implies it is a post-hoc verification step on a report you already hold, and the schema points back to ledger_compliance_report. However, there is no explicit 'use this when X, use Y instead' guidance against siblings such as ledger_check_receipt or ledger_report_pdf, so the agent must infer the routing.

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