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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description goes well beyond them: it discloses that the quote is live-pool, non-executable, unsigned, path-finding-free, excludes network/transfer fees, and enumerates the returned fields (amount in/out, pool fee, spot/effective price, price impact, utilisation, slippage bounds) as exact decimal strings at a validated ledger index. This is unusually rich behavioral context and supports the idempotentHint=false (live state changes).

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 dense sentences with the core purpose front-loaded and the critical caveat (indicative, non-executable, no keys) clearly separated. It is longer than minimal but each clause carries distinct information; only the enumeration of return fields could be trimmed if an output schema existed.

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, so the description correctly enumerates the return fields and their format (exact decimal strings at a stated ledger index). Combined with the safety/exclusion disclosures and full schema parameter coverage, an agent has everything needed to call and interpret this 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 coverage is 100%, so the baseline is 3, but the description adds meaning: it clarifies that direction supports 'either direction' and side supports 'an exact input or an exact output', and that slippageTolerancePct is optional and only used to derive a bound. This supplements the schema rather than merely restating it.

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?

Names a specific verb+resource (get_swap_quote) and pins it to the live ASTEROID/XRP AMM pool, stating it covers both directions and both exact-in/exact-out modes. This is clearly distinguishable from the sibling read-only analytics tools (get_liquidity_state, get_market_state, etc.) that do not return a swap estimate.

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 gives clear context for use and strong exclusions: 'INDICATIVE ONLY: it is not executable... models only the single AMM pool (no order books, no path-finding, no network or transfer fees), and this service never signs, submits or prepares a transaction.' It tells the agent when NOT to rely on it, though it does not name a sibling alternative for executable swaps.

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