Critical gaps across all dimensions. Tool definitions are sparse: 4 of 7 tools lack visible input schemas (enterprise_policy_search, hassantuk_home_protocol, open_meteo_villa_conditions, github_status, github_incidents defined in TypeScript file without schema verification). Descriptions are present but generic (avg ~60 chars, below 194-char baseline). No output schemas documented. No error handling guidance. Tool names lack clarity (e.g., 'open_meteo_villa_conditions' is domain-specific jargon; 'hassantuk_home_protocol' is opaque). Parameters present but descriptions are minimal. No evidence of idempotency, pagination, or composition patterns. STDIO transport caps protocol readiness at 50.

• Document output schemas for all 7 tools. Specify field names, types, and whether results are paginated. Example: 'Returns {contracts: [{id, name, status, inputSchema, outputSchema}], total: int}'.
• Rename tools for clarity: 'hassantuk_home_protocol' → 'read_ministry_interior_protocol'; 'open_meteo_villa_conditions' → 'get_weather_uae'. Start with action verbs.
• Add parameter descriptions with constraints. For 'scenarioId', specify format (UUID? alphanumeric?). For 'limit', add range (1-5). For 'latitude/longitude', document valid ranges (22-27, 51-57 already present but should be in description, not just name).
• Implement error handling guidance. Return structured errors: {error: 'not_found', message: 'Scenario not found', recovery: 'Call list_scenarios() to see available IDs'}.
• Consolidate tool definitions into a single Python registry using fastmcp decorators. Remove TypeScript tool definitions or auto-generate them from Python source.