manage_ens_name

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

With no annotations provided, the description carries the full burden. It discloses that this is a report (read-only behavior), lists what it returns, and states what it does not include (marketplace data). However, it does not explicitly use the word 'read-only' or mention any side effects, which is a minor gap given the tool name 'manage_ens_name' could imply mutation.

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 well-structured with a clear lead sentence and bullet-point return list. It is a bit longer than necessary but every sentence contributes value, including the sibling distinction. Front-loaded with the core purpose.

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 report-style tool with 2 parameters, no output schema, and no annotations, the description thoroughly covers what the tool returns, what it does not return, and how to use it. The enumerated return categories serve as a de facto output spec, making the description complete 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%, with both parameters (name and includeRenewalPricing) already described in the schema. The description adds minimal extra meaning beyond placing 'On-chain renewal pricing' in the return list, which implicitly connects to includeRenewalPricing. Baseline 3 is appropriate.

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 clearly states the tool's function as a 'One-shot management report for an ENS name' with a specific list of return items. It explicitly distinguishes itself from sibling tools like get_name_details, noting it is 'purpose-built for status/recommendation queries'.

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?

Provides explicit when-to-use guidance: 'ONLY tool you need' for management/status/recommendation queries, and directs users away from alternatives like get_name_details + get_valuation. Also specifies when to prefer a sibling: 'use get_name_details only if you need marketplace data.'

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