identity_transfer

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

With no annotations, the description carries the full burden and does disclose a key side effect: the transfer clears the agent wallet association. It also states the unlocked-wallet prerequisite, but omits irreversibility, ownership requirements, and fee/sponsored transaction 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 core action and side effect are front-loaded in a short, readable description. The closing earning_opportunities tip is somewhat off-topic for an identity transfer, but the overall text remains concise.

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 the core operation, a critical side effect, and the key prerequisite. Parameter details are fully covered by the schema, though the description does not mention transaction return behavior or irreversibility.

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 schema already explains agentId, recipient, fee, and sponsored. The description adds no parameter-level detail beyond implying the recipient is the new owner.

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: transfer an agent identity NFT in the ERC-8004 identity registry. This clearly distinguishes it from the generic transfer_nft sibling by naming the specific registry and asset type.

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 gives useful context: requires an unlocked wallet and says to run identity_set_wallet afterward if needed. However, it does not explicitly name alternatives or when not to use this tool.

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