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 adds genuinely new operational context by stating it is free and requires no key, which matters for an agent deciding whether to invoke it. It does not, however, disclose cost-free side effects, rate limits, or failure behavior.

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 tight sentence: the core action leads, the three sub-checks follow, and the cost/auth caveat closes. Every clause carries information; no filler.

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?

With no output schema, the description carries the burden of explaining what the agent gets back, and it says nothing about the result shape (e.g., a validity verdict, which check failed, failure reasons). The nested report object with additionalProperties=true is also left unelaborated. Adequate but with a real gap for a verification tool whose value is in its verdict.

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 already documents that it is the 'report' object exactly as received from ledger_compliance_report. The description adds nothing beyond that, so baseline 3 is appropriate.

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/check) and resource (compliance report), then enumerates the three concrete checks performed: hash recomputation, issuer confirmation, and blockchain anchor lookup. It is clear what the tool does, but it never distinguishes itself from the near-identical sibling ledger_check_receipt, so an agent must guess which of the two to pick.

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?

"Free; no key needed" gives useful preconditions, but there is no statement of when to use this versus ledger_check_receipt or ledger_audit_stream, and no exclusions or prerequisites beyond cost. Usage is only implied by the tool's purpose.

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