get_price

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

With no annotations provided, the description fully carries the burden. It discloses server-side caching (60-second update), error return on missing token or API unavailability, and implicitly indicates it is a read-only, non-destructive operation. No contradictions.

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 four sentences, front-loading the main action. Every sentence adds value—purpose, when to use, accepted formats, caching behavior, error handling. No redundancy or fluff.

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 tool has an output schema, the description covers key return fields (price, 24h change, market cap, volume) and error behavior. It addresses all relevant aspects for a simple single-token price tool, making it complete in context.

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 symbol accepts common symbols or full CoinGecko IDs, adding valuable context. However, it does not elaborate on the 'currency' parameter beyond what the schema (title and default) provides, leaving a gap in compensation.

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 retrieves current price, 24h change, market cap, and volume for a single token. It distinguishes from sibling 'get_prices' by explicitly noting it's for one token while get_prices is for multiple. Acceptable symbol formats are specified, making purpose unambiguous.

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 explicitly says when to use ('need live market data for one token') and when not to ('for multiple tokens, prefer get_prices'). It also mentions caching and error handling, providing clear context for invocation.

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