Five tools with clear verb-noun naming (get_*, search_*, check_*) and consistent descriptions (100-200 chars). All tools have input schemas with type definitions and parameter descriptions. Schemas are well-formed using Zod. However, output schemas are not formally documented, responses are inferred from code. Parameter descriptions include helpful context (e.g., 'Use test data instead of live data'). Error handling is minimal; no recovery guidance or actionable error messages. No tool annotations (readOnlyHint, destructiveHint). All tools are READ_ONLY, which is appropriate but unmarked.

• Add formal output schema documentation for each tool. Document the structure of the response object, field types, and what data is returned. E.g., get_status returns {eskom: {stage, stage_updated}, capetown: {stage, stage_updated}}.
• Add tool annotations: mark all tools with readOnlyHint=true since they are all READ_ONLY. This enables client-side optimizations and permission checks.
• Enhance error messages with recovery guidance. E.g., 'No areas found for "Xyz". Try a broader search term or use get_areas_nearby() with GPS coordinates.'
• Document parameter constraints formally. For area_id, specify the format (e.g., 'lowercase slug with hyphens') or provide an enum of valid IDs if the set is known.
• Add pagination support to search_areas and get_areas_nearby. Accept optional limit (default 20, max 100) and offset parameters. Return total_count so agents know if more results exist.