t2000_swap

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

Discloses that swap is not gasless and requires SUI for gas, and mentions the aggregator. No annotations exist, so description carries full burden. Lacks details on failure conditions or fee structure.

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?

Concise, front-loaded with main purpose, includes a note and CLI mapping. Every sentence is informative without redundancy.

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 core functionality and gas requirement. No output schema, but return value is typical for a swap tool. Could mention transaction result or output amount expectation.

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%, and description adds value by elaborating on token name formats (user-friendly or full coin types) beyond the schema's examples. Slippage default is already in schema.

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 swaps tokens on Sui using Cetus Aggregator, supports any token pair with liquidity, and distinguishes from sibling tools like send/receive/limit.

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 token names or full coin types, notes gas requirement, and references a CLI command. Does not explicitly contrast with t2000_limit or other alternatives.

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