Three tools with clear action verbs and basic schemas. All tools have descriptions (10-194 chars) and input parameters with type and description. However, output schemas are undocumented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., flight number format, registration pattern). No error handling guidance. Missing idempotency hints for read-only operations. Tool composition is sound (each does one thing), but descriptions could be more LLM-optimized per the 50-200 char baseline.

• Document output schemas for all three tools. E.g., search_flights returns {flights: [{ident, aircraft_type, origin, destination, ...}], status?: string}. iata_to_icao returns {icao_number: string} or {error: string}. aircraft_data_links returns {links: [{name, url}]}.
• Add format constraints to parameter descriptions. E.g., 'ICAO or IATA flight number (2-4 uppercase letters + 1-4 digits, e.g., UA123, UAL123)' and 'Aircraft registration (1-5 alphanumeric, e.g., N1234, C-ABCD)'.
• Add error recovery hints. E.g., iata_to_icao: 'If conversion fails, try search_flights() with the original number to find matching flights.' search_flights: 'If no results, verify the flight number format or try iata_to_icao() to normalize it.'
• Declare idempotency explicitly in tool descriptions. E.g., 'This is a read-only operation and safe to retry.' This signals to LLMs that transient failures can be retried without side effects.
• Add pagination support to search_flights. Accept optional limit (default 20, max 100) and offset parameters. Return total_count and next_offset in response. Document in description: 'Returns up to 20 flights; use offset for pagination.'

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry