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

Annotations already declare readOnlyHint and openWorldHint, so safety is partly covered. The description adds genuine context beyond that: it confirms nothing is signed or sent and previews exactly which values come back (slippage-adjusted minimum, price impact, route venues, fees in bps), which is useful for an agent deciding whether this is a dry-run.

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?

Front-loaded with the core action and result fields in one dense sentence, followed by two short caveats. The trailing 'Not investment advice' is marginally useful but is the least load-bearing clause; otherwise there is no waste.

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 carries the burden of describing returns and does so by naming the quote fields. Read-only behavior and slippage handling are covered, though the omission of any pagination/expiry or freshness note for quotes is a minor gap.

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 all four parameters are already documented in the schema, including the smallest-unit convention and slippageBps semantics. The description only alludes to slippage via 'minimum output after slippage' and adds no format or syntax detail beyond the schema, so 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?

States a specific verb and resource ('Get a swap quote on Solana through a DEX aggregator') and enumerates what the quote contains (expected output, minimum output, price impact, route venues, fees). The read-only clause implicitly separates it from the solana_swap_transaction sibling, though that sibling is never named.

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 implies usage context by declaring it read-only and unsigned, which suggests it is the preview step before executing a swap. However, it never explicitly says when to use this versus solana_swap_transaction or solana_token_price, leaving the routing inference to the agent.

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