erc8004__verify_attestation

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

No annotations are present, and the description only states the core action without disclosing behavioral traits like side effects, permissions, or edge cases. The agent gets minimal insight into behavior beyond the operation.

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 concise (two sentences) and front-loaded with the namespace label. It efficiently states the purpose without unnecessary words.

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?

Given a single parameter and no output schema, the description adequately explains the input purpose but omits details about return values (e.g., what 'intact' means, possible error states) or assumptions about the payload.

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 description adds context that the 'payload' parameter is used to recompute a content hash, partially compensating for 0% schema coverage. However, it does not specify structure, constraints, or accepted formats beyond the schema's 'additionalProperties: true'.

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 clearly states the tool's function: recompute a payload's content hash and report integrity status. The namespace prefix and 'MCP-native bridge to ERC-8004' distinguish it from sibling verification tools like trust__verify_attestation and compute-ledger__verify_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?

No guidance is provided on when to use this tool over alternatives (e.g., compute-ledger__verify_attestation, trust__verify_attestation). The agent must infer usage based on namespace.

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