Two tools with basic schemas and minimal descriptions. Both tools have proper input schemas with type definitions and parameter descriptions, but tool descriptions are extremely short (16-32 chars), falling well below the 50-200 char baseline for LLM-optimized descriptions. No output schemas documented. Error handling returns text but lacks recovery guidance or error classification. No parameter constraints (enums, ranges). Tools lack context about when to use them vs alternatives, prerequisites, or what data they return. Naming is clear (verb_noun pattern), but descriptions do not explain WHAT the tool does, WHEN to use it, or WHAT it returns, critical for LLM tool selection.

• Expand tool descriptions to 50-200 characters. Example: 'get-exchange-details: Retrieve trading volume, rank, and metadata for a specific cryptocurrency exchange (e.g., binance, coinbase). Returns current USD volume, trading pairs, and website URL. Use this to compare exchange sizes and liquidity.'
• Document output schemas explicitly. Define what fields each tool returns (e.g., get-exchange-details returns {name, rank, volumeUsd, percentTotalVolume, tradingPairs, exchangeUrl, updated}). Include field types and descriptions.
• Replace free-form string parameters with enums or constrained patterns. For 'exchange', define valid values: binance, coinbase, kraken, etc. For 'currency', define: bitcoin, ethereum, litecoin, etc. This prevents invalid API calls.
• Add error classification and recovery guidance. Instead of 'Failed to retrieve details for exchange: binance', return: 'Exchange not found: binance. Valid exchanges: binance, coinbase, kraken, huobi. Check spelling or call list-exchanges() to see all available exchanges.'
• Add tool annotations to the tool definitions. Mark both tools with readOnlyHint: true and idempotentHint: true so agents know they are safe to retry and do not modify state.