transfer

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

No annotations are provided, so the description carries full responsibility. It discloses a 1% platform fee and the api_key requirement, which are valuable. However, it lacks crucial behavioral context such as whether the transaction is reversible, the chain interaction, execution time, or potential failures. For a financial tool, these omissions are significant.

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 exceptionally concise: two sentences that convey purpose, fee, and a prerequisite. Every word earns its place with no redundancy or filler.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description covers purpose, a key behavioral trait (fee), and a prerequisite. However, it omits return values, error conditions, and post-transfer state, which are important for an agent executing a financial operation. It is minimally adequate but not complete.

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 description. The tool description adds minimal extra meaning beyond the schema (e.g., 'between agents or external wallet'). It does not clarify constraints like mutual exclusivity of 'to_agent_id' and 'recipient_address'. Baseline 3 is appropriate as the schema does the heavy lifting.

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'), the resource ('ERC-20 tokens'), and the scope ('between agents or to an external wallet'). This distinguishes it from sibling tools like 'transfer_cc' which likely handles credit card transfers. The verb-resource combination is specific and unambiguous.

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 description implies when to use (transferring ERC-20 tokens) and mentions a prerequisite ('Requires api_key'), but does not explicitly state when NOT to use or compare with alternative sibling tools such as 'transfer_cc' or 'accept_swap'. The agent must infer usage context without exclusions or guidance on alternatives.

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