Get current coin prices

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

Annotations already declare this a read-only, non-destructive operation, and the description adds the batching efficiency hint. However, it does not disclose potential rate limits, response size limits, or error behavior for invalid coin IDs. With annotations covering safety, the description contributes moderate context beyond the structured data.

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 two sentences with no fluff. The first sentence states the core purpose, and the second gives a key usage hint. It is front-loaded and every word earns its place.

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 the output schema exists and annotations provide safety, the description sufficiently covers the tool's purpose and the key batching behavior. For a simple read-only price look-up with all parameters documented, it is complete enough for correct selection and invocation.

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 each parameter already has meaningful descriptions (e.g., comma-separated CoinGecko ids). The description's mention of optional market cap, volume, and change mirrors the boolean parameters but does not add syntax or format details beyond what the schema provides. Baseline of 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?

The description clearly states a specific verb ('Get') and resource ('current prices for one or more coins in one or more currencies'), and lists optional data dimensions (market cap, 24h volume, 24h change). This distinguishes it from sibling tools like get_market_chart (historical) and get_coin_details (static info).

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 provides explicit guidance to batch multiple coins into a single call rather than making one call per coin, which is a clear when-to-use directive. It doesn't explicitly name alternatives or exclusions, but the purpose and batching instruction make the intended usage context clear.

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