The server registers 3 tools with fastmcp, all for reading Hong Kong health data. Tool definitions are present with names, descriptions, and input schemas. However, several quality gaps limit the score: (1) descriptions are minimal (90-115 chars), lacking context on when to use each tool or what structure is returned; (2) no output schemas are documented, LLMs cannot infer the shape of returned data; (3) parameters lack examples of valid district names, making the district filter in get_pas_gopc_avg_quota difficult for LLMs to use correctly; (4) error handling is implicit (rely on fetch_json_data) with no guidance for recovery. All tools are READ_ONLY, which is correct, but no tool annotations (readOnlyHint) are present in the code to signal this to clients. Parameter descriptions are adequate but not LLM-optimized.

• Add output schemas to all tools. Document the shape of the returned Dict: 'Returns {"data": [...], "last_updated": "ISO8601 string", "message": "optional string"}' with field types and examples.
• Expand tool descriptions to 150 - 250 characters. Include: (1) what it does, (2) when to call it instead of similar tools, (3) the output format, (4) any prerequisites. E.g., 'Fetches current AED waiting times (minutes) from Hospital Authority for all HA-managed hospitals in Hong Kong. Returns array of hospital records with department name and wait time. Language parameter controls output labels. Call this to show users real-time ED overcrowding status.'
• For get_pas_gopc_avg_quota, replace the generic district description with a concrete example list or enum. Either enumerate all 18 districts ('Tuen Mun', 'Central and Western', 'Eastern', ...) as an optional enum, or add: 'District name, e.g. "Tuen Mun", "Eastern", "Southern". Leave blank for all districts.'
• Add tool annotations via fastmcp. Use @mcp.tool(..., readOnlyHint=True) or equivalent to mark all three tools as read-only. This signals to clients that these tools are safe to call repeatedly without side effects.
• Wrap fetch_json_data calls in error handling with recovery guidance. If the API returns 404 or 500, catch it and return: {'error': 'Hospital Authority API unavailable. Retry in 30 seconds or inform user: "We cannot retrieve live data right now. Please try again shortly."'} rather than letting a raw exception propagate.
• Consider adding a discovery tool or resource that lists all available districts, specialties, or hospitals. This lets agents discover valid filter values without guessing.