erc8004__export_attestation

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

With no annotations, the description adds value by stating the output is unsigned, content-addressed, and requires the user's own signer for on-chain anchoring. This discloses key behavioral traits, though it does not mention idempotency or side effects.

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 a single, clear sentence that front-loads the purpose and context. While slightly jargon-heavy, it is concise and avoids unnecessary words, earning every sentence.

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 no output schema, no annotations, and no parameter descriptions, the description is incomplete. It does not explain the return format, the meaning of chain_id/token_id, or any prerequisites, leaving the agent underinformed.

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 does not explain the parameters (chain_id and token_id) beyond their existence. With 0% schema coverage, the agent receives no guidance on what values to provide or their meaning, which is a critical gap for a 2-parameter tool.

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 exports the agent's trust score as an unsigned ERC-8004 payload, using a specific verb ('export') and resource ('attestation'). It distinguishes from sibling tools like 'verify_attestation' or 'import_registration' by focusing on exporting for on-chain anchoring.

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?

The description implies the tool is used to export a trust score for on-chain anchoring, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites or when not to use it.

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