Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the payload contents, but since an output schema exists, that content listing is largely redundant and no other behavioral context (rate limits, freshness, coverage gaps) is offered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the resource and its payload before the argument note. Every clause earns its place, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and full annotation coverage, the description supplies the critical missing piece (accepted code formats) and the data scope. Only the when-to-use routing and edge-case behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the lone parameter has no description, so the description carries the full burden — and it does, specifying that 'airline' accepts either IATA (e.g. UA) or ICAO (e.g. UAL) codes with concrete examples. This is exactly the disambiguation an agent needs, though nothing is said about invalid or ambiguous codes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (airline profile) and enumerates its contents — identity, fleet, IOSA safety-audit registration, accident history, links — so an agent knows exactly what it returns. It is clearly distinct from sibling lookups like aircraft or airline_wifi, though the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over siblings such as aircraft, airline_wifi, or country_profile, and no preconditions or exclusions. The agent must infer usage from the resource name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.