swap_tokens

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

With no annotations, the description carries full burden but only offers '(DEX integration)' as a hint. It omits critical behavioral traits like whether it requires token approval, gas implications, irreversibility, or slippage handling for this financial mutation.

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?

The description is concise and front-loaded in a single sentence. However, it is under-specified for the tool's complexity, and the parenthetical '(DEX integration)' adds minimal value without structure.

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 a financial swap tool with four parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain token format, amount units, slippage behavior, return values, or any operational details needed by an agent.

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 description coverage is 0%, and the description provides no information about any of the four parameters (fromToken, toToken, amount, slippage). It does not compensate for the missing schema annotations at all.

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?

States a clear verb 'swap' and resource 'tokens', providing a specific action. However, it does not differentiate from sibling tools like find_best_swap_route or calculate_price_impact, leaving ambiguity about whether it executes the swap or just finds a route.

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 guidance on when to use this tool versus alternatives such as find_best_swap_route. The description provides no context, prerequisites, or exclusions.

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