get_prices

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

With no annotations, the description discloses important behaviors: same fields as get_price, graceful omission of unresolved symbols, acceptance of multiple symbol formats, and error conditions. However, it could mention rate limits or authentication requirements for fuller transparency.

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?

The description is concise at six sentences, each adding essential information. It is well-structured: purpose, usage guide, efficiency claim, field consistency, error handling, and input format. No redundant text.

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?

Given two parameters, no enums, an output schema, and sibling tools, the description covers purpose, usage, error behavior, and input constraints. It omits the list of supported currencies for the 'currency' parameter, but the default and context of cryptocurrency pricing mitigate this gap. Overall comprehensive.

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?

The input schema has 0% description coverage, so the description must compensate. It adds meaning for 'symbols' (accepts common symbols or CoinGecko IDs) but does not clarify valid values for 'currency' beyond the default 'usd'. The added value is partial.

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?

The description clearly states the tool gets current prices for up to 50 cryptocurrency tokens, using a specific verb ('get') and resource ('prices'), with constraints on batch size. It explicitly distinguishes itself from sibling 'get_price' by noting efficiency for multiple tokens.

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 gives explicit guidance: 'Always prefer this over multiple get_price calls when you need data for two or more tokens.' It also explains error handling (empty list or exceeding 50 tokens) and acceptable input types, providing clear when-to-use context.

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