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

Annotations only supply readOnlyHint=true, and the description adds real context on top: no auth required, ascending id ordering, and that the payload is untrusted citizen-authored data with a server-owned provenance boundary in CallToolResult _meta. The final READ-ONLY sentence partly restates the annotation, but the trust and auth disclosures are genuinely additive.

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 sentences, purpose front-loaded, minimal waste. The closing READ-ONLY clause is somewhat redundant with the readOnlyHint annotation and slightly over-explains what the annotation already conveys.

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 usefully characterizes the return (public attestations, provenance boundary in _meta) and the ordering, which is what an agent needs. It stops short of describing pagination or how since_id advances through the record, a minor gap for a refetchable list tool.

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 coverage is 0% with 4 undocumented parameters, so the description carries the burden. It names three of them (subject, issuer, class) as filters but omits since_id entirely and does not explain the class enum values, so it only partially compensates for the coverage gap.

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 gives a specific verb (Read) and resource (the public attestation record) plus the filter dimensions, so the agent knows exactly what the call fetches. It does not, however, distinguish itself from close siblings in the list such as 'attestation', 'issue_attestation', or 'chain_attestation', leaving that selection 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?

Usage is implied by the filterable-by-subject/issuer/class phrasing, but there is no explicit when-to-use or when-not-to-use guidance and no routing to the singular 'attestation' or 'issue_attestation' siblings. An agent can infer it is the list/read path but gets no boundary conditions.

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