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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious context: the Jupiter feed source, the 20-mint cap, the availability caveat on 24h change, and a $0.005 per-call x402 charge with an endpoint URL. Only return shape/pagination is left unstated.

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 sentences, with the core capability front-loaded before the cost/endpoint parenthetical. Nothing is wasted, though the raw URL is marginally less useful than a plain cost statement.

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-only pricing tool with no output schema, the description covers source, batch limit, what is returned (USD price plus optional 24h change), and the payment model. An agent has enough to invoke it correctly; only response structure is unspecified.

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 mints and payment are already documented in the schema, including the comma-separated format and trial-call behavior. The description restates the 20-mint limit but adds no new syntax or format guidance, so the baseline of 3 applies.

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 specific verb and resource: live USD prices for Solana token mints, sourced from Jupiter, batched up to 20. That clearly separates it from market-data siblings like token_pairs or token_search, though those alternatives are never named.

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?

The description implies usage (batch pricing lookups, per-call cost) but never says when to prefer it over token_pairs, token_search, or token_sell_check. Usage is inferable from the pricing model rather than stated.

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