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

Annotations already declare readOnlyHint and non-destructive behavior; the description's genuine contribution is 'public, no auth', which is useful auth context not encoded in annotations. Beyond that it adds nothing about scope, recency window semantics, or result volume — and 'recent' is left undefined.

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?

A single tight sentence with the substantive payload front-loaded and no filler. It is efficient, though the leading noun phrase buries the action the agent is trying to confirm.

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 zero parameters, an output schema in place, and annotations covering the safety profile, the description carries nearly everything an agent needs for correct invocation. The only meaningful omission is how it differs from transparency_latest and verify_proof.

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 tool takes zero parameters, so the schema requires no explanation and the description has no parameter semantics to compensate for. Baseline 4 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?

The description names the resource and its contents (ledger anchors, on-chain tx ids, credit supply at each anchor), but it is a noun phrase with no verb telling the agent what operation is performed — read, verify, or list. The name implies 'verify' while the text describes retrieval, and it does not distinguish itself from siblings like transparency_latest or verify_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?

There is no statement of when to call this versus transparency_latest or verify_proof, both of which sit in the same conceptual space. 'Independently checkable' hints at a verification use case but never converts that into an actionable condition.

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