transfer_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 of disclosure. It explicitly warns about FULL ownership transfer, recipient control (transfer, set records, let expire), and that resolver records are unaffected. It also reveals the auto-detection behavior for wrapped/unwrapped names, which is important operational context.

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 and front-loaded: the main purpose appears first, followed by detection logic, requirements, a warning, and a clarifying note about resolver records. Every sentence contributes meaningful information, and there is no redundancy or padding.

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?

The description covers prerequisites, automatic behavior, and consequences of transfer, which is good. However, there is no output schema and the description does not clarify what the tool returns or whether it submits the transaction or merely builds it. This ambiguity leaves a significant gap for an agent deciding whether to call the tool and how to interpret the result.

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?

The input schema already provides 100% descriptive coverage for all three parameters, including the example for 'name' and the 'must sign' note for 'fromAddress'. The description adds requirements but no new parameter-level semantics beyond what's already in the schema, so the baseline score of 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 opens with a specific verb+resource: 'Transfer ownership of an ENS name to another wallet address.' It goes beyond a generic statement by explaining the auto-detection of wrapped vs. unwrapped names, and the singular focus (as opposed to bulk_transfer_ens_names) is clear.

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 Requirements section gives clear preconditions (ownership, valid addresses, registered name) and the warning clarifies what this tool should be used for versus what it does not do (e.g., doesn't affect resolver records). It doesn't explicitly name alternatives like bulk_transfer_ens_names, but the context is clear enough.

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