get_price

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

With no annotations, the description carries full burden. It describes the return structure and notes that coin IDs are not ticker symbols. It does not mention rate limits, pagination, or error behavior, but provides sufficient behavioral clarity for a simple lookup tool.

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?

Well-structured with a clear purpose, usage note, parameter list, and return description. Slightly verbose but each sentence adds value; front-loaded with key information.

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?

Covers all parameters and return structure, including optional flags. Lacks mention of response size or rate limits, but is complete enough for typical usage given no output schema.

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 0%, so description must compensate. It explains each parameter in detail (coin_ids, vs_currencies, optional flags) with examples and a critical note about coin IDs not being ticker symbols.

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?

Clearly states it gets current spot price of one or more cryptocurrencies. Distinguishes from sibling tools by specifying it's for the cheapest, fastest current price lookup, contrasting with historical (get_market_chart) and venue-specific (get_exchange_ticker) tools.

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?

Explicitly recommends use for 'what is X worth right now?' and provides alternatives: for historical prices use get_market_chart or get_aggregated_ohlc, for real-time venue-specific prices use get_exchange_ticker.

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