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

Goes well beyond the readOnlyHint annotation by disclosing that the payload is untrusted citizen-authored data and that CallToolResult _meta carries a server-owned provenance boundary, which is critical injection-safety context. It doesn't cover failure behavior for a nonexistent id or any rate/latency characteristics, so it stops 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?

Three tight sentences, front-loaded with what is read and immediately followed by the auth and safety posture. No filler or repetition of the title.

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 does a good job of outlining the payload shape (attestation, disputes/retractions, chain anchor) even without an output schema, but the sole input parameter is left entirely unexplained, which is a real gap for an id-based lookup where wrong ids are the most likely failure mode.

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 0% and the description never mentions the single `id` parameter at all, so the agent gets no guidance on what identifier is expected, whether it is an attestation id versus another entity's id, or what an invalid value returns. With one undocumented parameter the description is expected to compensate and does not.

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 (Read) and a precisely scoped resource: exactly one attestation, plus its appended disputes/retractions and chain anchor. This distinguishes it from the sibling `attestations` (listing) and from adjacent tools like `chain_attestation` and `issue_attestation`.

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?

It supplies operational context ('No auth needed', 'READ-ONLY... can be repeated safely') that tells the agent when this call is appropriate, but it never names an alternative such as the plural `attestations` tool for enumeration or explains when to prefer one over the other.

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