dex_calculate_slippage

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

No annotations are provided, so the description carries the full burden. The verb 'Calculate' implies a pure off-chain computation without side effects, but it does not disclose the return format, rounding behavior, or that it is deterministic. The schema example for slippagePercent adds some context, but the description itself is minimal.

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 a single sentence of 10 words, fully front-loaded with the core purpose. Every word earns its place, with no redundant content.

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?

For a simple 2-parameter calculation tool with complete schema descriptions and no output schema, the description covers the essential purpose. However, it lacks explicit details about the calculation formula, return value type, and rounding behavior, which are relevant for a financial calculation. Still, given the tool's simplicity, it is largely complete.

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 100% with clear descriptions for both parameters ('Expected output amount' and 'Slippage tolerance percentage (e.g., 0.5 for 0.5%)'). The description text does not add any additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb 'Calculate' and a specific resource 'minimum output amount based on slippage tolerance'. This clearly distinguishes it from siblings like dex_get_swap_quote (which returns quotes) and dex_execute_swap (which executes trades).

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?

The description provides no information about when to use this tool versus alternatives, such as after obtaining a quote or to compute the minimum acceptable output before executing a swap. No exclusions or alternative references are given.

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