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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered structurally. The description adds genuinely useful context annotations cannot express: the call costs $0.001 via x402 in USDC on Base, and reverse lookups include forward-verification. It omits what happens on an unresolvable name or failed payment, which for a paid tool is a meaningful gap.

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 short sentences with no wasted words; cost is front-loaded, then purpose, then the usage cue. Slightly denser packaging (e.g. declaring the either/or parameter choice) would have earned a 5 without adding length.

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?

No output schema exists, so the description should carry the return shape; it implies an address or a primary name but does not describe the response format or error cases such as no reverse record. Given the complete input schema and rich annotations, this is adequate but leaves real gaps for a paid lookup tool.

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 both parameters are already documented in structured form and baseline is 3. The description clarifies the semantics of each direction (name-to-address vs address-to-primary-name) but never states that the two are mutually exclusive alternatives, leaving the agent to infer behavior when both or neither are passed (required count is 0).

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") plus the resource (Basename) and covers both directions explicitly: a name to its Base address, or an address to its primary Basename. The example (alice.base.eth) and the phrase "with forward-verification" make the operation unambiguous.

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?

"Use before sending funds to a name" gives a clear triggering context, which is more than most read tools offer. It does not say when not to use it or point to a sibling (e.g. usdc_payment_check or token_check) for post-resolution verification, so it stops just short of explicit routing.

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