ponzu_swap_tokens_for_eth

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

With no annotations, description carries the burden. It discloses automatic approval and underlying router function, but doesn't cover failure modes, gas implications, slippage handling beyond parameter, or return values. Adequate but not thorough.

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?

Two short sentences, front-loaded with core purpose. Efficient and clear, though could be slightly more structured with bullet points for prerequisites.

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?

Given no output schema and no annotations, description covers basic action and prerequisite but lacks context on slippage, failure, and related pricing check (sibling ponzu_calc_pricing). Adequate for a simple swap but leaves 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%, so baseline 3 is appropriate. Description adds no extra meaning beyond schema descriptions, though the mention of automatic approval relates to tokenAddress but not deeply.

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?

Description clearly states 'Sell tokens on PonzuSwap DEX for ETH', with a specific verb, resource, and target. It inherently distinguishes from the sibling 'ponzu_swap_eth_for_tokens' which is for the reverse direction.

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?

No explicit when-to-use vs alternatives, but the context of selling tokens for ETH is clear. The prerequisite of token approval is mentioned but no guidance on when not to use this tool (e.g., if approval not yet handled).

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