resolve_ens_basename

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

There are no annotations, so the description carries the behavioral burden. It usefully discloses that resolution produces on-chain cryptographic proof and that a 0.01 USDC fee applies on Base L2. However, it does not clarify the payment flow, whether payload may be a name or address, or any failure/edge-case behavior.

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?

The description is a single focused sentence followed by a parenthetical cost note. It front-loads the core purpose and contains no filler or redundant restatement of the tool name.

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 paid on-chain resolution tool with no output schema, the description tells the agent the expected result (EVM address) and cost, but it omits how to format the payload, whether the payment signature is required for execution, and what the returned proof looks like. This leaves some practical gaps for invocation.

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 the baseline is 3. The description's mention of `.base.eth` names and reverse ENS records gives some semantic hint about the payload, but it does not add concrete format guidance beyond what the schema already provides.

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 ("Resolves") and a specific resource (Base `.base.eth` names and reverse ENS records), and the outcome (EVM addresses) is explicit. This clearly distinguishes it from sibling verification tools such as verify_evm_signature or resolve_dns_over_https.

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 the intended use case through its domain-specific language, but it does not explicitly state when to prefer this tool over adjacent alternatives or what conditions should trigger its use. No exclusions or alternative tool names are given, so usage guidance is only implicit.

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