transfer_native_token

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that the tool signs and broadcasts a transaction, incurs gas fees, is irreversible, or returns a transaction hash. The description only states the basic action, which is inadequate for a fund-transferring operation.

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, front-loaded sentence with no filler. It efficiently conveys the core action and resource, making it concise and well-structured.

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?

For a write operation with no annotations and no output schema, the description is under-specified. It does not explain the return value (e.g., transaction hash), whether it waits for confirmation, or prerequisites like sufficient balance and gas. The schema handles parameters but lacks behavioral context, leaving the description incomplete for this action type.

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 has 100% coverage with detailed descriptions for all four parameters, so the description adds minimal value beyond the schema. It only references 'an address,' which mirrors the toAddress parameter without adding new meaning. The baseline score of 3 is appropriate given the schema's thoroughness.

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 verb 'Transfer' and resource 'native tokens (BNB, ETH, MATIC, etc.)', and specifies the destination 'to an address'. It distinguishes from sibling tools like transfer_erc20 and transfer_nft by limiting scope to native tokens, though it does not explicitly name alternatives.

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 usage for native token transfers but does not provide explicit guidance on when to use this tool versus alternatives such as transfer_erc20. No exclusions or alternative tool names are mentioned, leaving the usage context implicit.

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