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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed-world scope, so safety is covered. The description adds real value by enumerating what the response contains (hubs, mileage program, safety record, page link) in the absence of an output schema, but says nothing about behavior on an unknown slug or ambiguous identifier.

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?

A single front-loaded sentence with no filler, leading with the scope ('One airline in full') before the colon-delimited field list. The field list is slightly long but every item is informative given there is no output schema.

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 one-parameter lookup with no output schema, the field enumeration does the job an output schema would otherwise do. The only meaningful gap is the absence of any statement about failure modes or identifier format, which is minor for this tool shape.

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 100% and the schema itself documents the single 'airline' parameter as 'Airline slug or IATA code'. The description's mention of 'code' only echoes that; it adds no format examples, case sensitivity, or fallback behavior when a slug is not found.

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?

The phrase 'One airline in full' plus the field enumeration makes it unambiguous that this fetches a single airline's complete profile rather than a list. It does not explicitly contrast with get_airline_metrics, top_airlines, or list_airlines, so an agent must infer the boundary from those siblings' names alone.

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?

'One airline in full' implicitly signals single-record lookup versus the list_* siblings, but there is no explicit when-to-use statement, no mention of the alternative get_airline_metrics for metric data, and no prerequisite or error-condition guidance.

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