t2000_swap

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

Discloses that swap is not gasless and wallet needs SUI for gas (typically < $0.01). With no annotations, the description covers some behavioral traits but omits details like approval requirements or potential side effects.

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?

Description is short (3 sentences) and front-loaded with the primary action. No unnecessary words; every sentence adds value.

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 purpose, tokens, gas, and slippage. But lacks information about return values (e.g., transaction hash) which is important for a swap tool with no output schema.

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 parameter descriptions. The description adds value by listing example token names (SUI, USDC, etc.) and noting default slippage (0.01) and max (0.05), enhancing schema info.

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 the tool swaps tokens on Sui via Cetus Aggregator covering 20+ DEXs, supports any token pair with liquidity, and distinguishes from sibling tools (like send, pay) by specifying the swap action.

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 guidance on using user-friendly names or full coin types, mentions gas requirement and typical cost, and references CLI command for clarity. However, it does not explicitly state when not to use the tool or offer alternatives.

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