crypto.token-price

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention rate limits, data freshness, error handling for invalid IDs, or whether results are aggregated per asset. The description only states 'Price data by CoinGecko', which is insufficient for an agent to understand behavioral nuances.

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 long and immediately conveys the core purpose and key parameter details. Every sentence is essential, with no redundancy. It is well-structured and easy to parse.

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?

The description covers the tool's main functionality and parameters but lacks details about the output format (no output schema exists). It does not mention if results are returned as a single object or array per asset, or if pagination applies. For a simple price tool, this is a moderate gap.

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?

Both parameters are well-described in the schema (coverage 100%). The description adds value by explaining the ID format (lowercase, example list) and clarifying that 'vs' sets quote currencies. This extra context improves semantic understanding beyond the schema alone.

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 provides current spot price, market cap, 24h volume, and 24h change for crypto assets by CoinGecko asset ID. It specifies the ID format (lowercase, not ticker symbols) and explains the 'vs' parameter for quote currencies. This is specific and distinguishes it from sibling tools like crypto.tx or stocks.quote.

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 clear context: use this tool when you need crypto price data via CoinGecko IDs. It warns against using ticker symbols. However, it does not explicitly mention when not to use it or suggest alternatives among sibling crypto tools, so it's slightly lacking in explicit guidance.

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