ab_transfer_token

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

The description adds valuable behavioral context beyond the destructiveHint annotation. It discloses that the tool performs ENS resolution, automatically fetches token decimals, logs transaction hashes for explorer links, and requires a configured wallet signer. These are practical implementation details not captured in annotations.

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 efficiently structured with clear sections (FUNCTIONALITY, VALIDATION & LOGGING, COMMON USE-CASES). Each sentence earns its place by providing distinct information without redundancy. The front-loaded purpose statement immediately communicates the core functionality.

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 destructive tool with no output schema and incomplete parameter documentation, the description does well overall. It covers key behavioral aspects and parameter semantics. However, it doesn't explicitly mention error conditions, gas considerations, or what happens with native ETH transfers (no tokenAddress/tokenSymbol needed), leaving some gaps in completeness.

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?

With only 50% schema description coverage (two parameters undocumented), the description compensates well. It explains that tokenAddress or tokenSymbol are needed for ERC-20 transfers, clarifies that amount uses 'human units' (not wei), and mentions ENS support for the 'to' parameter. This adds meaningful context beyond the minimal schema descriptions.

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 tool's purpose with specific verbs ('transfer value') and resources ('from the caller's wallet to another address'). It distinguishes itself from sibling tools like ab_get_balance (which reads balances) and ab_deploy_token_erc20 (which creates tokens) by focusing on value transfer operations.

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 'COMMON USE-CASES' section provides clear context for when to use this tool (payout rewards, move faucet tokens, automation flows). However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the sibling tools, such as using ab_get_balance first to check funds.

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