crypto.token-price

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

Given no annotations, the description carries the burden. It discloses the data source (CoinGecko) and output fields, but does not mention rate limits, authentication, or data freshness. While it correctly indicates a read operation, additional behavioral details would improve 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?

Description is a single sentence that is front-loaded with the action and data returned. Every clause adds necessary context: input format, example, limitations, and source attribution. No superfluous words.

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?

For a simple tool with two parameters and no output schema, the description comprehensively covers input, output, and source. It answers likely agent questions: what data, how to format ids, and which currencies. The lack of output schema is compensated by specifying the data fields.

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% with descriptions. The description adds meaning beyond schema: clarifies format (lowercase CoinGecko asset id, not tickers), gives examples, specifies max 25, and notes default currency. The sentence 'vs sets quote currencies (default usd)' reinforces the schema description.

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 spot price, market cap, 24h volume, and 24h change for crypto assets. It specifies input format (CoinGecko asset id, lowercase, comma-separated) and distinguishes from siblings by focusing on real-time price data, not addresses or transactions.

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?

Provides explicit usage guidance: input format with examples, maximum 25 ids, and quote currency parameter with default 'usd'. Does not explicitly state when not to use or alternatives, but the specificity (CoinGecko ids, not tickers) and sibling list (no other price tools) make context clear.

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