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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond that: public RPC usage, a $0.005 USDC per successful call x402 payment model on Solana, and an equivalent HTTPS endpoint. It does not clarify failure charging or rate limits.

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 and front-loaded: resolution behavior comes first, followed by read-only access, pricing, and an HTTPS alternative. Every sentence carries useful information for an agent deciding whether and how to call the tool.

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 three-parameter resolver with no output schema, the description covers the main return semantics: an address plus optional text records on forward lookup, or a forward-verified primary name on reverse lookup. It also covers payment and transport, but does not address parameter conflict or detailed output shape.

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 description coverage is 100%, so the input schema already documents name, texts, and address. The description reinforces the forward/reverse distinction and text-record examples, but adds no syntax details or guidance on what happens if both name and address are supplied.

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 uses a specific verb, 'Resolve', and clearly covers both forward ENS-to-address resolution and reverse address-to-primary-name resolution, including optional text records. An agent can distinguish both modes without opening the schema.

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 clearly explains the two usage modes and the schema notes that address should be used instead of name for reverse lookup. It does not explicitly compare against sibling tools such as evm_read or domain_intel, so there are no named alternatives or exclusions.

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