t2000_swap

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

No annotations provided. Description mentions using an aggregator and user-friendly names, but omits that this is an on-chain transaction that will transfer tokens and incur gas fees. Basic disclosure is present but not detailed.

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 sentences with no wasted words. Front-loaded with the action and key details.

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 core purpose, scope, and naming conventions. Lacks details on return value and transaction effects, but given no output schema, it is largely sufficient.

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. Description adds value by clarifying that user-friendly names or full coin types can be used for from/to, which is not in the schema descriptions.

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 it swaps tokens on Sui via Cetus Aggregator (20+ DEXs), which distinguishes it from sibling tools like send, receive, or stake.

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?

It indicates when to use: for any token pair with liquidity on Sui. No explicit when-not or alternatives, but the context is clear given the sibling toolset.

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