Server has 5 tools with complete schemas and descriptions in both Zod and JSON-RPC formats. Tool names follow verb_noun pattern (query_*, list_*). Descriptions are present (avg ~80 chars) but lack actionable context for LLM selection. Parameters have types and descriptions, but lack enums for constrained values (e.g., zone_type, facility_type, status accept free-form strings instead of enums). No output schemas documented. Error handling exists but lacks recovery guidance. Missing tool annotations (readOnlyHint). Composition is sound, each tool has one responsibility.

• Convert free-form string parameters to enums. In mcp-server.ts, change zone_type to z.enum(['residential', 'commercial', 'industrial']), facility_type to z.enum(['park', 'school', 'road', 'market', 'parking', 'hospital']), and status to z.enum(['planned', 'approved', 'completed']).
• Document output schemas for each tool. Add a 'Returns' section to each tool description or create a separate schema file. Example: query_zoning_by_location returns {zoning_type: string, area_sqm: number, city: string, coordinates: {lat, lon}}.
• Enhance tool descriptions with WHEN-to-use context. Distinguish query_zoning_by_location (urban planning zones) from query_land_use_classification (103-category land use). Add: 'Use this for urban planning zoning (residential/commercial/industrial). For detailed land-use classification, use query_land_use_classification.'
• Add readOnlyHint: true to all tool definitions in mcp-server.ts. This signals to agents that these tools are safe to retry without side effects.
• Improve error messages in tool implementations. Instead of generic isError: true, return specific guidance: {isError: true, content: 'Invalid coordinates: latitude must be 21.9 - 25.3, longitude 120.0 - 121.9. Provided: [lat, lon].'}