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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds material context: the $1,000 liquidity floor, why it exists (round-trip quotes on dead curves look fine), that errors surface as isError and are not charged, and that calls are free. Only missing pieces are rate limits and any upstream throttling behavior.

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-loads the output shape, then rationale, then routing, then pricing/error semantics — each sentence carries distinct information. Slightly dense with a parenthetical server URL, but nothing is filler.

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 one-parameter read tool with full annotations and an output schema, the description covers purpose, routing, the non-obvious liquidity threshold, and error/cost behavior. An agent has everything needed to call it correctly and interpret the 'dead token' flag.

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% with a single well-described parameter (base58 pattern, 1-100 items), so the schema does the heavy lifting. The description reinforces the address-not-symbol constraint and the 100-item cap but adds no format or batching detail beyond what the schema states, matching the baseline 3.

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+resource (USD price, 24h change, liquidity) with scope (up to 100 Solana mints) and a distinctive behavior (flags illiquid/dead tokens under $1,000 liquidity). An agent can immediately tell this is a batch Solana mint spot-price tool and distinguish it from symbol-based or other-chain pricing.

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?

Explicit 'When to use' clause names the selection condition: Solana mints by address here, majors/other chains by symbol via crypto_price, including where that sibling lives. That is exactly the when/when-not/alternative triad.

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