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

With no annotations, the description carries the full burden, and it does disclose the non-obvious economics: a $0.01 charge settled via x402 in USDC on Base or Solana. It also enumerates the returned fields (freshness, chain, liquidity). It stops short of failure modes, per-call vs per-ticker billing, or rate limits.

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?

Three compact sentences, cost front-loaded, no filler. It is dense and jargon-heavy (x402, xStocks, Ondo), but every clause contributes to an agent's decision.

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?

For a 2-parameter, no-output-schema, unannotated tool, the description supplies cost, coverage universe, returned fields, and input modes, which is nearly everything needed to invoke it. Only the sibling routing and error/billing behavior are left open.

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 description coverage is 100%, so both parameters are already documented in the schema and 'One ticker, up to 10, or tickers=all' largely restates them. No extra syntax, precedence rules, or examples (e.g. what happens if both are supplied) are added.

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?

States a concrete output ('each token's price per share vs the real stock reference, premium/discount %, freshness, chain and liquidity') for a named asset class (xStocks on Solana, Ondo Global Markets). An agent knows exactly what this returns, though it never explicitly distinguishes itself from the sibling get_token_liquidity.

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?

No when-to-use, when-not, or alternative guidance is given. The input modes ('one ticker, up to 10, or tickers=all') describe how to call it, not when to prefer it over get_quote, get_token_liquidity, or other siblings.

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