bulk_transfer_ens_names

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

With no annotations provided, the description carries full transparency burden. It discloses automatic detection of wrapped/unwrapped names, full ownership transfer implications, the fact that resolver records are unaffected, and ownership prerequisites. This is thorough behavioral disclosure beyond the schema.

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 summary, benefit statement, key capability, requirements list, warning, and follow-up note. Every section earns its place, and the formatting with bullets and headers improves scannability. It is slightly long but appropriate for a tool with complex behavior and safety implications.

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?

Despite lacking an output schema, the description fully covers what an agent needs to know: what the tool does, prerequisites, batch limits, automatic type handling, side effects (full ownership transfer, resolver records untouched), and a recommended next step. This is complete for a transaction-type tool without return values.

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 baseline is 3. The description echoes parameter meanings already present in the schema (array of name+recipient pairs, fromAddress as owner). It adds a small nuance about same/different recipients, but does not introduce new syntax or details beyond the schema. Thus, it meets but does not exceed the baseline.

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 action: 'Transfer multiple ENS names in a single transaction via Multicall3 — bulk send.' It specifies the resource (ENS names), the verb (transfer), and the batch method, distinguishing it from the single-transfer sibling tool by emphasizing 'multiple' and 'much cheaper and faster than transferring names one at a time.'

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?

It explicitly promotes this tool over single transfers ('much cheaper and faster'), sets clear requirements for use (ownership, valid addresses, registered names), and suggests a follow-up tool ('consider using bulk_set_records'). This gives the agent concrete guidance on when to choose this tool and what conditions must hold.

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