Two tools with complete schemas and descriptions. search_flights has excellent parameter coverage (25 params, all typed and described) with detailed constraints (time formats, weekday enums, defaults). search_airports is minimal but functional. Both tools lack output schema documentation, LLMs cannot predict response structure. No error handling guidance, no tool annotations (readOnlyHint), no recovery paths. Descriptions are adequate (194 and 72 chars respectively) but lack dependency hints or when-to-use context. Parameter descriptions are generally good but some lack format constraints (e.g., 'H:MM' format stated but not formalized).

• Document output schemas for both tools. For search_flights, specify: returns array of {flight_id, airline, departure_time, arrival_time, price, currency, stops, duration}. For search_airports, specify: returns array of {code, name}.
• Add error handling guidance. E.g., 'If no flights found, try expanding date range or removing filters. If airport code invalid, call search_airports() first.'
• Add readOnlyHint: true to both tool definitions in list_tools() to signal they are safe to cache and parallelize.
• Add limit and offset parameters to search_flights to support pagination. Cap results at 50 flights per call and document this limit in the description.
• Enhance search_airports description to include: 'Call this first if you have an airport name but not the IATA code. Returns up to 50 matches sorted by relevance.'