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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses Ethereum-mainnet-only scope, a 10-minute cache, and a per-call price of $0.002 with x402 payment via USDC on Base or Solana — genuinely actionable context an agent cannot get from annotations. It does not describe failure behavior for unresolvable names or unverified reverse records, leaving a modest gap.

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 definition is compact and front-loaded: direction, network, record types, input rule, caching, then pricing. The opening clause largely duplicates the title, which is a minor waste, but the remaining sentences each add distinct information.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating the profile text records returned (avatar, url, description, email, socials). Combined with the cost and caching disclosures, an agent has enough to call this correctly; only the response envelope shape and no-result behavior remain unspecified.

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 only 33% (only `tx` is documented, and thinly), so the description must compensate — and it does by explaining that `name` drives forward resolution and `address` drives reverse resolution, and that one or the other should be given. The `tx` payment parameter is left to the schema's one-line note and the x402 mention, so the payment flow is only partially clarified.

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 names a specific verb (resolve) and resource (ENS names/addresses) and explicitly spells out both directions: forward name -> address and verified reverse address -> primary .eth name, plus text-record retrieval. This is more than the title restated and makes it clearly distinct from siblings like evm_address or domain. It stops short of naming a sibling to contrast against, which keeps it at 4.

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?

'Give either name or address' establishes that one of the two inputs selects the operation mode, which is useful usage framing. However, there is no guidance on when to prefer this over evm_address/domain, no statement about what happens if both or neither are supplied, and no exclusions. Usage is implied rather than prescribed.

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