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

readOnlyHint=true already tells the agent this is a safe read, so the description doesn't need to re-establish safety. It adds genuinely useful context about what the payload contains — the hashing and on-chain verification procedure for sealed claims — but says nothing about whether the spec is static, versioned, or how large it is, which matters for a zero-parameter doc fetch.

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 front-loaded sentence fragment with no filler. It is efficient, though the fragment form (no verb) costs a little immediate readability compared with 'Returns the machine verification spec…'.

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 and an output schema present, the description only needs to convey what domain of spec this is and why an agent would fetch it — which it does. The one missing piece is any cue about how this spec relates to the attest/attest_status workflow it describes.

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 no parameters at all, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing argument behavior for an argument-free call.

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?

Names a specific resource — the machine verification spec for the attestation service — and scopes its contents (hashing of sealed claims, on-chain anchoring, independent verification). That distinguishes it from generic spec siblings such as instrument_spec or standing_spec. It never uses a verb ('returns'/'get'), so the agent must infer it is a retrieval tool, which keeps it below a 5.

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 guidance on when to call this versus the many adjacent siblings (attest, attest_status, attestation_stats, proof_spec, receipt_spec, delivery_spec). No preconditions, no exclusions, no mention that it is a read-the-docs style endpoint rather than an action.

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