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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint), so the bar is lower; the description still adds real context by stating the data is 'ledger-indexed' (a snapshot, not live), clarifying the fee is a protocol LP-vote fee rather than a token tax, and explaining how the accessibility verdict is derived from master/regular keys and signer list.

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 dense sentence that is front-loaded with the resource identity, which is appropriate. It is packed tightly (four commas plus parenthetical) but nearly every clause maps to a returned field, so little is wasted.

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 has to carry return-value semantics, and it does so by naming the pooled reserves, LP supply, fee, and per-account fields. What is missing is any mention of pagination, freshness, or filtering scope, but for a zero-parameter snapshot tool this is largely complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4.

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 (ASTEROID/XRP AMM state) and enumerates exactly what it returns: pooled reserves, LP supply, trading fee, per-account LP share and accessibility verdict. The closing 'Not a quote' explicitly separates it from quote-oriented siblings like get_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 'Not a quote' clause gives one useful exclusion against get_swap_quote, but there is no positive statement of when to prefer this over the closest sibling get_liquidity_stats, nor any prerequisites. Guidance is implied rather than explicit.

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