erc8004__verify_attestation

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

With no annotations, the description must fully disclose behavioral traits. It states the tool is read-only (recompute and report) but omits details like whether it requires on-chain access, rate limits, or what 'intact' means in the context of ERC-8004 attestations.

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 description is one sentence (plus a bracket prefix). It is short but could be clearer by removing the prefix and integrating domain context more naturally.

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 tool involves ERC-8004 on-chain identity and has no output schema. The description lacks details on payload structure, return value format, and verification semantics, making it insufficient for correct invocation without external knowledge.

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 only parameter is `payload` (object), described only as 'payload' with no added meaning. Schema coverage is 0%, and the description does not explain required fields, structure, or how the hash is computed from it.

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 specifies the action ('recompute content hash' and 'report intactness') and identifies the domain (ERC-8004 identity). However, it does not differentiate this tool from sibling verify_attestation tools (e.g., trust__verify_attestation), which share the same verb and output concept.

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?

No guidance on when to use this tool versus other verification tools. There is no mention of prerequisites, input constraints, or scenarios where this tool is appropriate.

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