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

Annotations already mark this as mutating and destructive. The description adds useful behavioral constraints: only 'available' balance, only an 'owned' wallet, and only the wallet's 'verified EVM-bound address' as destination. It does not contradict the destructive hint.

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?

Single front-loaded sentence with no filler; the key action and restrictions are stated immediately.

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, open-world mutation with no output schema and three required parameters, this description leaves out important operational context: amount units, idempotency behavior, how to get withdrawal status, and failure semantics. The sibling get_withdrawal_status suggests async tracking that is never explained.

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 0%, and the description does not mention amountMinor units, walletId ownership semantics beyond 'owned wallet,' or the purpose of idempotencyKey. This is a material gap because the agent must infer parameter meaning from names and schema constraints alone.

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?

States a clear verb ('Transfer'), asset ('test-USDC'), source ('owned wallet'), and destination constraint ('verified EVM-bound address'). This differentiates it from siblings like send_payment and request_testnet_funding.

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 gives clear context: use for moving available test-USDC out of an owned wallet only to its verified EVM-bound address. It does not explicitly name alternatives or say when not to use, so it falls short of a full routing rule.

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