Two tools with complete input schemas and descriptions, but significant gaps in output documentation and error handling guidance. search_airports returns a list but lacks pagination/limit parameters and output schema documentation. search_flights returns a dict but the schema is not documented in the code. Both tools have reasonable descriptions (100-150 chars) but lack actionable error recovery guidance. Parameter descriptions are present but some lack format constraints (e.g., cabin_class enum not enforced in schema, adults range not documented). Error handling returns dict objects with error fields, but does not guide the LLM on recovery steps.
Search for airports by name, city, or IATA code.
Search for flights between two airports.
Output schemas not documented. search_airports returns list[dict] with fields {title, skyId, entity_id} but this is inferred from code, not declared in docstring. search_flights returns dict with session_id and buckets but structure is not documented. LLMs cannot plan downstream calls without knowing response shape.
cabin_class parameter accepts free-form string ('economy', 'premium_economy', 'business', 'first') but is not declared as enum in schema. LLMs may hallucinate invalid values. Schema shows type:string with no enum constraint.
Error responses return dict with error/message fields but do not guide recovery. E.g., 'AirportNotFound' error does not suggest calling search_airports() to discover valid codes. 'BannedWithCaptcha' suggests 'Try again later or use a proxy' but does not tell LLM whether to retry or escalate.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
search_airports lacks pagination. No limit or offset parameters. If query returns 100+ airports, response will be huge and waste tokens. Baseline pattern requires limit/offset and total count.
adults parameter description says '1-8, default: 1' but schema does not enforce min/max constraints. LLM could pass 0 or 100 and cause API error. Constraints must be in schema, not just docstring.