Africa API MCP demonstrates solid fundamentals: all 8 tools have clear verb-noun naming (list_, get_, query_), comprehensive descriptions (100-200 chars typical), and explicit Zod schemas with type constraints. Tool annotations (READ_ONLY) are properly declared. However, several parameter descriptions lack actionable detail (e.g., 'Sort field' without specifying valid values), and output schemas are not formally documented, responses are returned as JSON strings without declared field structures. Error handling is present but generic (HTTP status codes without recovery guidance). The server correctly uses structured content attachment for JSON responses, but lacks pagination metadata (total count, next_cursor) in list operations.

• Document output schemas for each tool. Add a comment block or separate schema definition showing the structure of returned objects (e.g., 'list_countries returns {countries: [{code, name, capital, region, area, currencies, languages}], total, page, per_page}').
• Replace free-form parameter descriptions with enums or patterns. For 'sort' in list_countries, change description to 'Sort field: one of name, region, area, population' and add enum constraint in Zod schema.
• Add pagination metadata to list responses. Include 'total' count and 'next_cursor' or 'has_more' flag so LLMs know when to stop paginating and avoid context window exhaustion.
• Enhance error messages with recovery guidance. Instead of throwing 'HTTP 401', throw 'Authentication failed (HTTP 401). Set AFRICA_API_KEY environment variable, get a free key at https://africa-api.com/dashboard.' This guides the LLM to self-correct.
• Simplify query_data parameter design. Split into separate tools (query_data_single_country, query_data_multiple_countries) or document mutual exclusivity explicitly in each parameter description to prevent ambiguous calls.