transfer

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

The openWorldHint annotation indicates a state-changing operation, which matches the transfer action. However, the description does not disclose important behavioral aspects such as whether approval is needed, the irreversibility of the transfer, or how chainId affects execution. The description adds little beyond what the annotation already implies.

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, compact sentence with no superfluous words. It is front-loaded and directly states the operation, making it highly scannable and efficient.

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 a complete schema, the description fails to address contextual complexity: it does not mention chain selection, token approval prerequisites, decimal handling, or what the return value represents. Since this is an openWorldHint operation with many sibling tools, the description is too sparse for an agent to use it confidently in diverse scenarios.

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 every parameter already has a detailed description. The tool description adds no extra parameter semantics; it only repeats the general concept. Baseline of 3 is appropriate because the schema carries the explanatory weight.

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 a specific verb (Transfer) and resource (an ERC20 token to an address), making the core purpose unambiguous. It does not explicitly differentiate from sibling tools like evm_transfer_erc20 or send_token, but the purpose is nevertheless 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?

There is no guidance on when to use this tool versus alternatives. With many sibling tools that perform token transfers, the lack of any usage context or exclusionary language leaves the agent without sufficient information to select this tool correctly.

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