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

With no annotations, the description bears full responsibility for disclosing side effects. It reveals the cost, payment networks, and auto-bridging, but fails to mention that the withdrawal is irreversible (funds are moved out) and contradicts itself by saying ETH while the schema says USDC. The missing permanence and internal inconsistency undermine trust.

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 concise and front-loaded with the purpose and return, then includes important usage notes, cost, and a link. The trailing metadata blocks ([paymentNetworks], [pricing]) add noise but do not excessively inflate the size. It earns a 4 for efficiency.

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?

The description covers the core function, return value, cost, payment networks, and provides a link for further details. Missing are explicit statements about irreversibility, minimum balance, or failure modes. The currency inconsistency reduces completeness. Overall, adequate but with gaps.

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% with clear descriptions for both parameters, so baseline is 3. The description adds little beyond calling the destination 'a specified address' and introduces a currency conflict (ETH vs USDC) that could mislead the agent about parameter usage.

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 (withdraw accumulated ETH from Flipr agent wallet to a specified address) and mentions the return (transaction hash). It distinguishes from siblings as no other tool handles withdrawals. However, the inconsistency between 'ETH' in the description and 'USDC' in the input schema introduces ambiguity about the actual asset withdrawn.

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?

Explicitly states when to call: 'Only call this when you want to cash out' and warns that ETH in the agent wallet is needed for future flips. This provides clear usage guidance and a reason to avoid unnecessary use, even though no alternative tool is mentioned.

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