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

Goes well beyond the annotations by disclosing the 0.075% fee taken from amount, the 0.10 USDC minimum, expected latency (~10 seconds), the return timing contract ('returns once it has arrived'), and the custody guarantee that 'the money never leaves your own wallets'. For a non-idempotent, non-read-only mutation, these are exactly the traits an agent needs.

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?

Purpose is front-loaded and the sentences earn their place, though naming sentUsdc/receivedUsdc duplicates the output schema. Slightly long but well organized and free of 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?

With full schema coverage, annotations covering the safety profile, and an output schema for return values, the description supplies everything else an agent needs: fee economics, timing, custody, and the routing guidance. Nothing required to call it correctly is missing.

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 coverage is 100%, so the schema already documents both parameters, including that amount is a decimal string and the fee comes out of it. The description's gloss on 'from' ('the network the USDC leaves; it arrives on the other') largely restates the schema, so the baseline 3 applies.

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 specific verb and resource with tight scope: move USDC between the managed agent wallet's own Solana and Base sides. It also distinguishes itself from the transfer/payment siblings by noting they 'already move what they need', so an agent can tell this apart from agent_wallet_transfer without opening either schema.

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?

Gives explicit when-to-use ('fund Base ahead of a run of Base payments') and when-not ('payments and transfers already move what they need'), plus the second valid case ('bring everything back to Solana'). Alternatives and the condition selecting them are spelled out rather than left to inference.

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