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

With no annotations, the description carries the burden and does well: it discloses the per-call cost ($0.001 USDC) and enumerates return fields, both non-schema information. It omits quote expiry/validity window and whether the quote is a reusable executable payload, which matter for a swap quote.

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?

Three short sentences, front-loaded with purpose, then returns, then usage imperative, then cost. No filler and nothing buried.

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?

With no output schema, the description compensates by naming the returned fields (amount out, price impact, route, fees). Remaining gaps are quote lifetime and whether an execute-swap tool exists as a next step; minor but real for a trading-adjacent 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 description coverage is 100%, with units, base58 formatting, and the slippage default all documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Specific verb and resource: 'Get a Jupiter swap quote for any Solana token pair,' plus an explicit list of what the response contains. Jupiter/Solana pair quoting is clearly distinguishable from the many price, liquidity, and prediction-market siblings.

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?

'Essential before executing any trade' gives a clear call condition and sequencing hint. It stops short of naming alternatives (e.g. order_book_aggregator, dex_liquidity) or stating when a quote is unnecessary, so it is clear context without exclusions.

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