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

Annotations already mark it read-only and open-world, and the description adds important behavior: on-chain, deterministic, no LLM, plus payment requirements via x402. It also provides a sample output, though it does not discuss failure modes or latency.

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 front-loaded and mostly efficient, with purpose, examples, determinism, output sample, and payment details. The opening 'ENS / Basename resolve' is slightly redundant with the tool name, but the rest earns its place.

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?

For a simple one-parameter read-only resolver, the description covers purpose, input forms, output example, execution model, and payment requirements. An agent has enough information to invoke it correctly without an output schema.

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?

Schema coverage is 100%, so the single input parameter is already documented. The description adds useful semantics beyond the schema by showing both accepted input forms and the bidirectional resolution behavior.

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 states a specific verb/resource: resolve ENS/Basename names to addresses and addresses to primary ENS names. It gives concrete examples for both directions, making the tool's purpose immediately clear. No sibling tool appears to overlap directly.

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 clearly explains the two supported input forms and what each returns, which tells an agent when this tool is appropriate. It does not name alternatives or explicit exclusions, but there are no obvious sibling alternatives for this capability.

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