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

With no annotations, the description carries the full burden. It usefully discloses the data source (Ethereum mainnet, read directly) and the paid-over-x402 cost model at $0.005/call, which matters for invocation. It omits failure behavior: what happens when a name is unregistered or an address has no reverse record, and whether results can be stale.

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 core action is front-loaded in the first sentence, with cost/source detail trailing. The middle sentence ('Names are what humans paste...') is rhetorical but does clarify the practical purpose; only mild trimming is possible.

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?

No output schema exists, yet the description never states what is returned (an address string, a primary name, or nothing when unresolvable). For a tool with two optional parameters and zero required ones, it also leaves the 'supply exactly one' contract unstated, though the source and pricing context are covered.

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 baseline is 3. The description adds only the reverse-resolution meaning of the address parameter ('an address back to its primary ENS name'), which is modest value on top of the schema's own 'Use instead of name' note.

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?

Names a specific verb (resolves) and resource (ENS name) and covers both directions of resolution (name→address and address→primary name). No sibling in the evm_* family does ENS resolution, so an agent can distinguish it immediately.

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 use case (converting between human-readable names and chain-usable addresses) and notes it reads Ethereum mainnet directly. However it never states when to prefer one direction, nor routes the agent away from an alternative, and gives no guidance that exactly one of name/address should be supplied.

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