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

With no annotations, the description carries the burden and handles pricing explicitly ($0.001 USDC per call, x402 on Base), which is critical for an agent deciding whether to invoke. It also clarifies that reverse results are forward-verified, implying a reliability caveat. Missing: what happens if both name and address are omitted (schema requires neither), and failure/timeout behavior.

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?

Two front-loaded clauses covering capability, format examples, and price with no filler. It is dense but every element (records list, forward-verified, pricing) earns its place; it could be split for readability but nothing is wasted.

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-param tool with no output schema and no annotations, the description covers the return shape (avatar, url, twitter, github, description), the reverse-lookup guarantee, and the payment model. Only the neither-param case and error behavior are unaddressed, which is a minor gap.

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 both parameters are already documented with examples (vitalik.eth, alice.base.eth). The description adds modest value by enumerating the record types returned, but adds no syntax, format, or mutual-exclusion guidance for the two optional params. Baseline 3 is appropriate.

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 (resolve), the exact resources (ENS / Basename names and addresses), and both directions of lookup. It is unmistakably distinct from siblings like chainread_token, chainread_read_contract, and chainread_multicall, which imply token/contract reads rather than name resolution.

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?

Clear about which input selects which behavior — pass a name for forward lookup with records, pass an address for reverse primary-name lookup. No explicit exclusion or sibling routing is given, but the tool's domain is narrow enough that the context is unambiguous.

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