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

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial fact that this call costs $0.01 USDC on Base via x402, plus the returned fields (address, avatar, profile text records). That payment/return context goes meaningfully beyond the annotations, though latency or failure modes for the payment flow are unstated.

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 compact, front-loaded sentences with no filler; the purpose leads and the price/return details follow. The 'Input: name' clause is slightly redundant with the schema but negligible.

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 correctly names what comes back (wallet address, avatar, profile text records) and discloses the x402 payment cost. For a one-parameter read tool this is nearly complete; only the payment/error flow is 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 0% and there is a single required 'name' parameter, so the description must carry the load. It supplies a format example ('jesse.base.eth') which helps, but does not cover the 3-100 character constraints or normalization rules beyond what the schema implies.

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 a Base name ... to its wallet address') and gives a concrete example ('jesse.base.eth'). This is clearly distinguishable from the numeric/state-reading siblings like base_balance or base_token.

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?

Usage is implied by the single-purpose lookup framing, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many base_* siblings. An agent can infer the intent, but nothing routes it explicitly.

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