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

With no annotations, the description carries the full burden and does meaningful work: it discloses the 10-ticker cap, that data may be delayed, and that pricing is 0.002 USDC per call via x402. It does not say what happens on partial/invalid symbols or whether a failed call is still billed.

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?

Two dense sentences with zero filler: the first covers the payload and scope, the second covers the two caveats an agent most needs (delay, cost). The most decision-relevant information is front-loaded.

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 two-parameter read tool with no annotations and no output schema, the description names the returned fields, the symbol limit, staleness, and the payment model — enough to call it correctly. Missing only failure/partial-symbol behavior, which is a modest gap.

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 the ticker format and the 402 payment-proof dance are already fully documented in the schema. The description adds only the 'up to 10 tickers' limit, which is useful but marginal against a schema that already explains both parameters in detail.

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 precisely what is returned (latest price, change, day range, volume, exchange) for a bounded set of tickers, and gives concrete symbol examples including index and crypto tickers. It does not explicitly distinguish itself from siblings like crypto_price, ohlcv, or token_market, so the agent must infer the boundary.

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?

Usage is implied by the 'up to 10 tickers' scope and the examples, and the x402 note hints that a payment step precedes a successful call. There is no explicit when-to-use guidance (e.g. 'use ohlcv for historical bars' or 'use crypto_price for spot-only crypto') and no stated exclusions.

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