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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description then supplies the part annotations cannot: exactly which fields come back (ratings, airside terminal change, per-terminal lounge status, rating and page link). With no output schema, that return-shape disclosure is the description's main contribution.

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 sentence, front-loaded with the lookup key and then the payload, with no filler or restatement of the title. Every clause carries new information about what the caller receives.

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 read tool with no output schema, the description covers the critical gap by enumerating return contents. It stops short of stating error behaviour for an invalid IATA code or whether lounge lists can be large, minor omissions for a lookup call.

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?

There is only one parameter and the schema already documents it at 100% coverage ('IATA code (e.g. SFO) or airport slug'). The description restates the same IATA-or-slug duality without adding format details, fallback behaviour for an unknown code, or slug-resolution rules, so it adds little beyond structured data.

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 description names a specific verb-and-resource pair (fetch one airport) and enumerates the payload: editorial ratings, airside terminal-changeability, terminals with lounges. That is enough to distinguish it from list_airports and search_terminals without opening a schema, though it never explicitly names those siblings.

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?

The singular 'One airport by IATA code or slug' implies a lookup-once use case, but there is no explicit when-to-use or when-to-prefer-an-alternative guidance (e.g. use search_terminals or get_lounge for narrower needs). Usage must be inferred from the phrasing.

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