get_price

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

No annotations are provided, so the description carries the burden. It identifies the data source (CoinGecko) and the output fields (spot price, percentage changes). However, it does not discuss rate limits, caching, update frequency, or error handling, which would enhance 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 exceptionally concise: two sentences that front-load the purpose and then provide parameter details. Every sentence adds unique value with no redundancy.

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?

With no output schema, the description partially compensates by listing the return values (spot price and changes). However, it lacks detail on the exact response structure (e.g., array or object) and other common fields like market cap or volume. Given the tool simplicity, it is adequate but not thorough.

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 coverage is 100% (both parameters have descriptions). The description adds value by clarifying that 'ids' must be CoinGecko IDs (with examples like 'bitcoin,ethereum') and that 'vs' defaults to usd, supplementing the schema with practical usage guidance.

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 returns 'Spot price + 24h / 7d / 30d change' for tokens via CoinGecko, distinguishing it from siblings like get_history_prices or get_ohlc which serve different time-series needs.

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?

It specifies the required field 'ids' with proper formatting (CoinGecko IDs, not exchange tickers) and explains the optional 'vs' parameter defaults to usd. However, it does not explicitly suggest when to use this tool over alternatives (e.g., for current vs historical data).

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