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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description goes beyond that by disclosing cost ("Free"), the anchoring chain (Base, eip155:8453), the daily cadence, the serving path /attest/<day>.json, and a concrete verification workflow including EIP-712 signatures per row — real behavioral context an agent could not get from structured fields.

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?

The critical qualifier ("Free") is front-loaded, followed by the resource, the record shape, and the verification recipe in a tight three-sentence block. Dense with domain jargon (keccak256, EAS UID, EIP-712), but every clause carries information a verifier needs.

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?

An output schema exists, so return values need not be explained. The description still covers what a record contains, how to verify it, where the referenced file lives, and where to read governance, which is everything needed to call a zero-parameter read tool correctly.

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 there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies a full dump rather than a parameterized query.

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 a specific resource (daily on-chain attestations) and defines its exact granularity (one record per store day) with the fields each record carries. This cleanly separates it from the sibling fixing tools (index_fixing, tokens_fixing), which expose the fixings themselves rather than their on-chain attestations.

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" and the pointer to /governance imply context, and the verification procedure (re-hash the file bytes, compare against fixingsHash) implies the primary use case of independent verification. However, there is no explicit routing such as "use this instead of index_fixing when you need an auditable anchor," so usage is only implied.

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