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

With no annotations, the description carries the behavioral burden well: it discloses reverse records are forward-verified to prevent name spoofing, that XRPL .xrp names are detected but resolved:false, and that the call is free. It does not mention auth requirements or rate limits, but the safety-relevant behaviors are covered.

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?

Front-loaded with the core purpose, then param, then behavioral caveats. Every sentence earns its place, though the parameter restatement is slightly redundant with the schema and the return-field list makes it dense.

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 resolution tool with no output schema, the description compensates by enumerating the return shape ({ query, kind, namespace, chain, resolved, address, name, sources }) and the XRPL failure case. Error handling and latency are unaddressed but the core contract is complete.

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 the schema already documents q. The description still adds value by enumerating the accepted input forms (ENS/Basename name, EVM 0x address, XRPL r-address) and the auto-detection behavior that determines how q is interpreted.

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 states a specific verb and resource ('Bidirectional name <-> address resolution for ENS (name.eth) and Basenames (name.base.eth)') and names the parameter. An agent can immediately distinguish this from lookup_wallet or caller_id because the ENS/Basename and XRPL scope is explicit.

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 context is implied by 'Auto-detects direction' plus the XRPL caveat, so an agent knows the tool handles both forward and reverse lookups. However, it never says when to prefer this over siblings like lookup_wallet, nor any when-not conditions beyond the XRPL unresolved note.

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