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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: it lists the quote's contents and explicitly warns nothing is executed, preventing an agent from mistaking a quote for a trade. Permissions/pricing-tier details are absent.

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?

A single front-loaded sentence plus a four-word safety clause. Every element earns its place, and the non-execution warning sits at the end where it is most likely to be read as a qualifier.

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?

There is no output schema, and the description compensates by enumerating the returned fields (received amount, minimum after slippage, price impact, route). For a read-only quote tool with 4 simple flat parameters, an agent has everything needed to select and call it.

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 75%; 'from', 'to' and 'amount' are well documented in the schema. The description mentions slippage only obliquely via 'minimum after slippage' and never explains the units or bounds of slippage_bps, which is the one parameter the schema leaves undocumented. Baseline 3 for high-coverage schemas 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?

The description names the resource (swap quote), the venue/aggregator (Jupiter on Solana), and the exact output fields (tokens received, minimum after slippage, price impact, route). A specific verb is implied by 'quote' and reinforced with 'executes nothing'. It does not explicitly contrast with read-only siblings like get_price, so it falls just short of the top mark.

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?

'Quote only; executes nothing' usefully fences the tool off from any execution intent, but there is no guidance on when to prefer it over get_price or a future swap-execution tool, nor any prerequisite/rate-limit context. Usage is implied rather than stated.

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