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

Beyond annotations, the description adds operational context including response size (32 KB), rate limit (60 RPM), demo vs L402 payment access, and HTTP 400 on invalid input. These details help an agent plan calls without guessing about access, rate limits, or error behavior.

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 front-loaded with purpose and usage guidance, then packs operational details tightly without wasting sentences. Every clause contributes either selection guidance or invocation context.

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 the output schema exists, the description need not explain return values. It covers purpose, when to use it, the main alternative, access/payment mechanics, rate limits, defaults, and error handling, making it complete for correct invocation.

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%, so the schema already documents both parameters and the execution_venue enum. The description only repeats that it accepts 'pair' and that execution_venue defaults to 'uniswap_v3_public', adding little semantic value beyond the 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 names a specific verb, resource, and scope: it evaluates DEX swap parameters against pool depth and mempool visibility to quantify MEV sandwich risk and compute optimal slippage tolerance. It also explicitly distinguishes itself from compare_crosschain_bridge_routes.

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 states exactly when to use the tool: configuring slippage tolerance and private-RPC routing before executing an on-chain DEX swap. It also names the alternative tool and condition for cross-chain bridge route comparison.

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