SkyMate defines 4 tools with clear verb-noun naming (search_*, build_*) and basic descriptions. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are minimal (10-60 chars), falling below the 50-200 char baseline for LLM-optimized docs. Output schemas are not documented, LLMs cannot predict response structure. Error handling is absent; tools return generic 'not found' messages without recovery guidance. No parameter constraints (enums, ranges) despite accepting free-form strings like airport_iata. The 'limit' parameter lacks bounds documentation. Tools are read-only (good for safety) but lack idempotent/readonly annotations.

• Expand tool descriptions to 80-150 chars. Example: 'search_flight_status: Retrieve real-time status, gate, and terminal for a specific flight by IATA code (e.g., AA100). Returns flight status, departure/arrival times, and aircraft info. Use when tracking a known flight; use search_departures/arrivals to discover flights.'
• Document output schemas in tool descriptions or as structured comments. Example: 'Returns {found: bool, result_count: int, flight: {flight_iata, flight_status, departure_iata, arrival_iata, arrival_terminal, arrival_gate, ...}}'
• Add parameter constraints: 'limit: integer, 1-100 (default 6). Maximum flights to return. Larger values may timeout.'
• Enhance error messages with recovery hints: 'No flight found for AA100. Verify IATA code format (airline + 3 digits). Try search_departures(airport_iata="SFO") to see available flights.'
• Add tool annotations via FastMCP: @mcp.tool(annotations={"readOnlyHint": true, "idempotentHint": true}) to signal safety to LLMs.