spraay_swap_quote

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

Annotations provide readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds behavioral context beyond annotations by specifying the cost ($0.002 USDC) and the platform (Uniswap V3 on Base). It does not contradict any annotations.

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 only two sentences, front-loaded with the main action, and includes a prerequisite and cost. Every sentence adds value with no 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 is a quote retrieval with an output schema, the description covers the essential elements: platform, chain, output details, prerequisite, and cost. It could mention time-sensitivity of quotes, but that is not critical. Overall, it is sufficiently complete for an agent to use correctly.

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 detailed parameter descriptions. The tool description adds minimal parameter information but does not re-explain them, which is acceptable. The mention of return details ('expected output amount, price impact, and route details') provides context for the output but not for parameters. Baseline 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 clearly states the tool's purpose: 'Get a swap quote from Uniswap V3 on Base.' It specifies the output (expected output amount, price impact, route details) and is distinct from siblings like spraay_swap_tokens (which shows available tokens) and spraay_swap_execute (executes swap).

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 directs users to use spraay_swap_tokens to see available tokens, which is helpful context. It also notes the cost ($0.002 USDC) as a usage consideration. However, it does not explicitly mention when not to use this tool or distinguish it from other quote tools like spraay_solana_jupiter_quote or spraay_bridge_quote.

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