The Free Crypto News MCP server defines 10 tools with basic descriptions and input schemas. However, there are significant quality gaps across the definition quality dimension. All tools lack output schema documentation, which violates a critical pattern (pattern:tool). Tool descriptions are present but minimal (average ~60 chars, below the 194 char baseline for A+ tools). Parameter descriptions are sparse, most parameters have only a single sentence. No error handling guidance is provided in any tool description. The tools lack security considerations (API key injection, rate limiting, result capping). Tool composition is reasonable (each tool does one thing), but the output schemas are completely undocumented, forcing LLMs to infer response structure.

• Add output schema documentation to every tool. For get_crypto_price, document: 'Returns object with fields: coin (string), symbol (string), price (number), change_24h (number), market_cap (string), updated_at (ISO 8601 string).' This enables LLMs to extract the right fields and plan downstream operations.
• Expand tool descriptions from ~50 chars to 100-200 chars. Include WHEN to use each tool and how it differs from related tools. Example: 'Retrieves the latest crypto news headlines sorted by publish date. Use this for a general market overview. For breaking/urgent news with sentiment analysis, use get_breaking_news instead.'
• Add error handling guidance. E.g., 'If coin not found, returns error with list of supported symbols. If API rate limit exceeded, wait 60 seconds and retry.' Document expected HTTP status codes (404 for unknown coin, 429 for rate limit).
• Document pagination behavior for list tools. E.g., 'Accepts limit (max 100, default 20) and offset (0-indexed). Returns object with articles array and total count. Use offset + limit for pagination across large result sets.'
• Add explicit format constraints to string parameters. E.g., coin parameter: 'Cryptocurrency name (case-insensitive, e.g., bitcoin, Bitcoin) or symbol (uppercase, e.g., BTC, ETH). Leading/trailing spaces are trimmed. Returns error with available symbols if unrecognized.'
• Clarify the semantic difference between get_breaking_news and get_crypto_news. Add to both descriptions: 'Breaking news focuses on high-impact market events with priority indicators. General news is chronological headlines without priority filtering.'