get_coin_details

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

No annotations, but description states it returns formatted markdown with all available market data, which is a key behavioral detail. Does not mention auth, rate limits, or error handling, but for a read-only tool this is adequate.

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?

Three concise sentences: first lists capabilities, second output format, third usage hint. No wasted 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?

Single parameter, straightforward. Description covers return content in detail despite lacking output schema. Could mention error cases for invalid coin_id, but overall complete.

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 already describes coin_id with examples (bitcoin, ethereum). Description adds 'single coin by ID' but doesn't add new meaning beyond the schema. Baseline 3 is appropriate due to 100% schema coverage.

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 comprehensive details for a single coin by ID, listing many specific data points (price, market cap, changes, etc.). Distinguishes from siblings by naming search_coins for finding the ID first.

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 guidance to use search_coins first, implying proper sequence. Lacks explicit comparisons with other siblings like get_price_history or get_market_overview for when to use this vs. alternatives.

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