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

Annotations already mark this read-only and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the return contents (avatar, profile text records) and, importantly, that it is a paid call at $0.003 USDC on Base via x402.

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 tight sentences: the action and output first, then the payment prerequisite. Nothing is padded and the payload is front-loaded.

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 single-param, no-output-schema tool, the description covers input format, output contents, and cost. It stops short of covering payment mechanics (automatic vs. manual x402 settlement) and failure behavior for unregistered names, which keeps it from a 5.

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 0%, so the schema gives no help for 'name' beyond type and length bounds. The description compensates with a concrete format example (jesse.base.eth), which is the key semantic detail needed for a single, otherwise self-evident 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 (Resolve) and resource (Basename, with example jesse.base.eth) and names the output (address plus avatar and profile text records). No sibling tool performs name resolution, so an agent can place 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 when to use it (you have a .eth-style name and need the underlying address) and adds a cost signal, but never states when to prefer it over alternatives or what happens for unresolvable names. Usage is inferable rather than explicit.

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