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

With no annotations, the description carries the full burden and does disclose meaningful operational traits: the data source (viem over public Ethereum mainnet RPCs), the L1-scoping caveat, and a pay-per-call model ($0.02/call USDC on eip155:8453). It stops short of covering failure behavior (unresolved names), rate limits, or confirmation/latency characteristics.

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?

Three sentences, front-loaded with purpose before the operational caveat and pricing. The 'ENS name ↔ address, bidirectional' clause partially restates the opening sentence, and the stray lowercase 'eNS' is sloppy, but overall it is tight and every sentence carries 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?

For a 2-parameter tool with no output schema, the description covers what it produces (addresses or ENS names), the network/source, the payment model, and the L1 caveat. Nothing critical is missing for correct invocation, though error/edge behavior is left implicit.

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, but the description adds real meaning the schema lacks: it maps the two enum values to their directions ('resolve' = name → address, 'lookup' = address → ENS name), which the schema only labels as 'Operation'. This resolves ambiguity about what each op accepts for the loosely-named 'value' parameter.

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?

States a specific verb and resource (resolve ENS names to addresses), names the reverse direction explicitly (address → ENS name), and specifies the mechanism/network (viem against Ethereum mainnet). This is clearly distinguishable from neighboring crypto tools like crypto_address_validate or crypto_tx_explain.

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 sentence 'Use this when an agent needs to ENS name ↔ address, bidirectional on Ethereum mainnet' gives a clear usage context plus the network scope, and the note that ENS data lives on L1 regardless of wallet's active chain is a useful usage signal. However, it names no alternative tool or when-not-to-use condition.

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