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

Beyond the readOnly/openWorld/idempotent annotations, it discloses that the data is live ("Current"), that the trading fee is a protocol pool fee set by LP votes and "can change at any time," and flags its deprecated status. It doesn't cover rate limits or exact freshness guarantees, but the added behavioral context is substantive.

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?

The deprecation warning is correctly front-loaded and the trade fee unit gotcha is worth stating, but the field-by-field explanation of tradingFeeUnits/tradingFeePct/tradingFeeBps is dense and somewhat repetitive. Still, each clause carries information relevant to interpreting the response.

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 and no parameters, the description carries the full burden of explaining the return payload, and it does so thoroughly (pooled amounts, LP supply, fee units and percentage, locked vs community split). An agent has everything needed to interpret the result and avoid misuse as a price.

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 no parameter semantics to explain; the 4 baseline applies. The description appropriately spends its space on output semantics instead.

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?

It names the specific resource and scope ("Current ASTEROID/XRP AMM pool data: pooled XRP and ASTEROID, LP token supply, trading fee, locked vs community LP split"), so an agent knows exactly what it returns. It also explicitly distinguishes itself from the sibling get_liquidity_state by marking itself deprecated in favor of it.

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?

It gives an explicit migration directive ("Deprecated — use get_liquidity_state") and a hard exclusion ("This is not a quote and must not be used to price a swap"). Both when-to-use (only for current pool stats) and when-not-to-use are covered.

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