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

With no annotations, the description carries the full burden and excels: it discloses the data source (XRPL DEX/AMM), error behavior (ok:false with reason when pair unknown/unreachable), data integrity (never invented prices), cost, and parameter constraints. This is exceptionally transparent.

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 description is concise and front-loaded with the core definition, then parameter details, source, and error behavior. The cost and feedback call-to-action are useful context but not strictly necessary for tool invocation, so it is slightly less tight than a 5.

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?

Given no output schema and moderate parameter complexity, the description covers purpose, parameter syntax, data source, error behavior, and pricing. It leaves the successful return envelope implicit but adequate; a bit more detail on the exact response structure would make it a 5.

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 0%, so the description compensates well by explaining interval (5|15|60|240|D|W), bars (max 1000), and fx ('USD'). Issuer and currency are inherently clear from the XRPL token context, though not explicitly detailed, which keeps this from a 5.

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 clearly identifies the tool as providing OHLC price-history candles for an XRPL token, specifying open/high/low/close and volume per interval. This directly distinguishes it from sibling tools like verify_price (price verification) and check_xrpl_token (token metadata).

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 clear context that this is for historical price data behind candlestick charts and explains parameter usage (interval, bars, fx). However, it does not explicitly mention when not to use it or name alternative tools, so it misses the full bar for explicit exclusions.

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