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

With no annotations, the description carries the full burden, but it does add genuine value by disclosing the cost model ($0.004 USDC per id). It does not cover auth requirements, rate limits, error behavior, or return format, which leaves real gaps for a paid external-provider call.

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 short sentences, front-loaded with the core purpose and then the cost/limit detail. Every clause earns its place with no 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 simple one-parameter batch lookup this covers purpose, scope, and cost adequately, and no output schema exists so return values need not be explained. But it omits sibling routing against cortex_prices/cortex_token_price and any auth or failure context, leaving the agent under-informed on selection.

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% and there is a single parameter fully documented with an example and 1-50 bounds. The description's '1-50 ids' merely restates the schema constraint, so baseline 3 is appropriate.

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 (batch spot USD prices for many coins) and provider (CoinGecko), which distinguishes it from single-token lookups. However, it does not explicitly name or differentiate from close siblings like cortex_prices or cortex_token_price, so the distinction is left to inference.

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 word 'Batch' implies use when pricing many coins, but there is no explicit when-to-use guidance, no mention of when to prefer a single-token tool, and no named alternatives among the many price-related siblings. The agent must guess the routing.

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