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

Goes well beyond the readOnly/idempotent annotations: discloses that a best route far worse than the $100 quote is flagged `large_price_impact`, that the premium is withheld when the reference listing isn't the token's company, and that a stale saved quote is labelled with its age. It also discloses the paid pathway ($0.003 USDC via x402, first call included) and that failed tokens cost nothing, which is exactly the operational context an agent needs.

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 scope, then drilled into quote detail, caveats and pricing in descending priority. The long enumeration of routes/sizes is dense but each clause carries information; a small trim of the repeated 'paid-only' phrasing would tighten it.

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 carries the return-shape burden and does so thoroughly: it enumerates expected output, LI.FI minimum, effective price, premium/discount, best-route naming, and flag/withhold conditions. Combined with the payment and staleness caveats, an agent has everything needed to call and interpret it.

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 both parameters are already documented; the description adds meaning beyond that by tying the token to the Robinhood Chain (4663) stock-token universe and naming the accepted ticker examples, and by framing the paid-only retry behavior that x_payment enables. It doesn't add format/syntax detail beyond the schema, so it sits just above baseline.

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 opens with a specific verb and resource ('Read indicative quotes for a Robinhood Chain (4663) stock token') and gives concrete examples (TSLA, NVDA). No sibling tool in the list reads on-chain quotes, so the agent can disambiguate it from otto_prepare_stock_buy or otto_tokenized_equities immediately.

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?

Clearly states the context of use ('indicative only: not a firm quote and not a transaction, nothing to sign, gas excluded') and preconditions (paid-only, including the first call; a token the route does not quote is refused). It does not explicitly name a sibling alternative for getting a firm/executable price, which keeps it below a 5.

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