sol_swap_quote

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

Annotations (readOnlyHint=true, destructiveHint=false) are supported by the description, which adds context as 'Free API' and 'Jupiter aggregator.' However, no further behavioral details (e.g., rate limits, precision) are disclosed beyond the 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?

Two sentences, no redundancy. Purpose is front-loaded, and every word is necessary. No filler or unnecessary details.

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 exists, so the description should explain the return format (e.g., quoted amounts, price, slippage). It does not. Additionally, it lacks guidance on when to use this tool versus the sibling sol_swap or swap_quote, making it incomplete for an agent.

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%, and the description adds value by clarifying that 'Any SPL token vs SOL/USDC' is supported, which is not obvious from the basic parameter descriptions (e.g., 'sol, usdc or base58 mint'). This enhances understanding of parameter usage.

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?

Description clearly states the tool provides a Solana DEX quote via Jupiter aggregator for any SPL token against SOL/USDC. The verb 'quote' and specific resource (Solana DEX, Jupiter aggregator) differentiate it from siblings like evm_swap or swap_quote.

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 mentions 'Free API,' suggesting no cost, but does not explicitly state when to use this tool versus alternatives like sol_swap or swap_quote. It implies use for quoting before swapping but lacks explicit guidance or exclusions.

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