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

No annotations provided. Description implies read-only lookup from CoinGecko, but does not explicitly state non-destructiveness, rate limits, or error handling for unknown coins. Adequate but lacks full behavioral disclosure that would be expected without annotations.

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?

Two sentences, no wasted words. First sentence defines purpose and output, second sentence gives usage guidance. Front-loaded with essential information, quick 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?

For a simple lookup tool with one parameter and no output schema, the description explains what is returned (USD price, change, market cap) and data source. Missing explicit mention of response format or error cases, but covers the main context needed for an AI agent to decide usage.

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?

Only one parameter 'symbol' with 100% schema coverage and a detailed schema description listing many coin tickers. The tool description adds no new semantic info beyond what the schema already provides, meeting the baseline but not exceeding it.

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?

Description clearly states 'Real-time cryptocurrency price lookup for any coin', lists popular coins (BTC, ETH, SOL, etc.), and specifies returned data (live USD price, 24h % change, market cap). It distinguishes itself from sibling tool 'market_pulse' by explicitly saying not to use that for specific coin prices.

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 states when to use: 'for ANY "what is X price", "X price now", "how much is X", or "X USD" query.' Also gives clear exclusion: 'Do NOT use market_pulse for specific coin prices — use this tool.' Names alternative tool.

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