Execute a swap

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

No annotations, so description fully covers behavior: dryRun safety, amountIn cap, minAmountOut enforcement via slippageBps or explicit, Permit2 flow, output to signer, and private key requirement for actual send. Highly transparent.

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 and well-structured. Main action in first sentence, safety details in bullet-style paragraph. No wasted words. Front-loaded with core purpose.

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?

No output schema, but description explains return behavior (plan for dry run, transaction for real). Covers all key aspects: inputs, safety, requirements, and result. Complete for a complex swap tool.

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%, baseline 3. Description adds value by explaining dryRun default and safety, amountIn cap, slippageBps default, and recipient restriction, beyond 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?

Clearly states it executes an exact-input single-hop swap via Uniswap v4 UniversalRouter. Distinguishes from siblings (rhc_info, get_positions, quote_swap) by focusing on execution rather than info or quoting.

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 when to use (executing a swap) and key safety guidelines (dryRun defaults to true, amount cap, minAmountOut enforced). Implicitly suggests alternative quote_swap for quotes. Lacks explicit when-not-to-use, but context is sufficient.

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