Build an EIP-8004 registration document (no chain access)

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

Annotations already mark this as read-only and idempotent, and the description reinforces and expands on that by saying it does not touch Solana and instead produces a local JSON document and self-contained data URI. This makes the behavioral contract clear, including the fact that the output can be previewed before actual on-chain registration without 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 compact—two sentences—and front-loaded with the core output artifact before moving to usage scenarios. Every sentence adds useful information, and there's no redundant restating of the schema or annotation fields.

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?

Despite having 12 parameters, the schema covers them and the description provides the missing operational context: what artifact is produced, that it is self-contained data URI, how it relates to on-chain sibling tools, and how to use it in the hosting flow. The lack of an output schema doesn't hurt because the description names the concrete output format clearly.

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 input schema achieves 100% coverage of paramater descriptions, so the schema does the heavy lifting. The description does not add parameter-level semantics beyond the schema, though it connects the resulting artifact to registration_uri. This lands at the baseline for high schema coverage.

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 purpose: 'Build the Genesis-style EIP-8004 registration-v1 JSON document and its self-contained data:application/json;base64 URI.' It also differentiates from sibling tools by explicitly noting 'without touching Solana' and by referencing what mint_onchain_agent / register_agent_identity will write on-chain.

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?

It explicitly tells the agent when to use the tool: to preview what mint_onchain_agent / register_agent_identity would write on-chain, or to host the document independently and pass it back as registration_uri. The 'without touching Solana' phrase also communicates the when-not: this is the offline/read-only path, not the on-chain execution path.

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