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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low; the description goes further by cataloguing the returned fields and flagging that profile text is owner-written and untrusted — a genuine security caveat not present in any structured field. It also pins the authoritative location of payable addresses, preventing trust in spoofed profile links.

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 sentences, zero filler: the first front-loads the payload inventory, the second delivers the trust caveat and field redirection. Every clause earns its place.

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 is the only place return values are described, and it does that thoroughly for a single-record lookup, plus a trust warning. Only minor gaps remain (no mention of behavior for unregistered/malformed names, which the siblings or errors presumably handle).

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% and the single 'name' parameter is fully documented with accepted forms (DNS, .cns, .eth), so the schema carries the burden. The description adds only the notion of a 'registered name' — no format or resolution-order detail beyond what the schema says. Baseline 3 applies.

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 enumerates exactly what resolving a registered name yields — owner, expiry, profile, X badge, payment addresses — which is a concrete resource+operation statement. It distinguishes itself implicitly from reverse_lookup (address→name) and check_name (availability) by being the record-fetch, but never names a sibling explicitly.

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 only implied: an agent infers 'resolve a name to inspect its records.' The clause 'payable addresses are only in "payments"' is a useful field-selection hint but stops short of routing the agent to get_payment_address or explaining when check_name/reverse_lookup would be preferable. No when-not guidance is given.

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