sell_token

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

Discloses balance check, scaling via percentage, and tax effects. However, no annotations exist, and the description omits side effects, authorization requirements, rate limits, or transaction details like confirmation steps.

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?

Three compact sentences with no wasted words: purpose, usage hint, and critical tax warning. Front-loaded and efficient.

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?

Covers the main selling action, balance check, percentage, and tax, but misses context for the 'to_usdb' parameter (stopping at MAINTOKEN). No output schema exists, but a brief note on return values would improve 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?

Schema coverage is 100% so baseline is 3. The description adds meaningful context for 'percentage' (scaling out) and 'slippage_percent' (accounting for tax differences), exceeding the schema's detail.

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 action ('Sell a token for USDB'), identifies the resource (token), and adds check-balance and percentage scaling hints, distinguishing it from sibling tools like buy_token or bet.

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?

Provides explicit guidance on using percentage to scale out and adjusting slippage based on token tax rates (1.5% vs 0.5%). Does not specify when not to use the tool or mention alternatives, but the advice is actionable.

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