spraay_swap_execute

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

The description states the tool returns unsigned transaction data, meaning it does not broadcast the transaction. It also discloses the cost ($0.01 USDC). This adds significant behavioral context beyond the annotations, which already declare readOnlyHint and destructiveHint as false.

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 three sentences long and front-loads the core action, followed by output details, prerequisite, and cost. Every sentence adds value without redundancy.

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 tool's complexity, the description covers the essential aspects: what it does (swap on Uniswap V3 on Base), output (unsigned tx), prerequisites (get quote), and cost. The presence of an output schema further supports completeness.

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 baseline is 3. The description does not elaborate on the parameters, but the schema already provides adequate descriptions for all 5 parameters.

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 the tool executes a token swap via Uniswap V3 on Base, specifies the output as unsigned transaction data, and distinguishes from the sibling tool spraay_swap_quote by advising to get a quote first.

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 explicitly directs the agent to first get a quote using spraay_swap_quote and mentions the cost ($0.01 USDC). It does not list alternative tools or when not to use, but the prerequisite is clear.

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