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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds genuine context beyond that: the payload is 'lightweight', contains codes plus names, and is intended to be downloaded once and filtered client-side, implying no pagination. It still omits any statement about result size or rate limits for a full-table read.

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?

Front-loaded 'Overview' followed by clearly labelled sections; an agent can skim and act. There is mild redundancy (the code/name return content is restated in both 'What You Get' and 'Quick Start'), and the section scaffolding is heavy for a one-parameter tool.

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?

With no output schema, the 'What You Get' section usefully compensates by naming the returned fields. However, it leaves the required-vs-optional parameter question ambiguous and says nothing about result volume or pagination for a full airport list, so an agent calling it correctly still has avoidable uncertainty.

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%, so the baseline is 3, and the description does add meaning by explaining that `q` filters by name OR code, beyond the schema's bare 'Search query'. But it also states 'Call with no parameters to get all airport codes and names' while the schema marks `q` as required and additionalProperties=false, which could push an agent into an invalid call.

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 verb and resource: retrieve a lightweight list of airport IATA codes paired with names. An agent immediately knows this is a bulk code/name lookup. However, it never distinguishes itself from close siblings such as get_data_flights_airports, get_data_flights_airports_iatas_iatacode, or get_data_iatacodes, so the agent must infer the boundary.

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 'When to Use' section gives three concrete scenarios (autocomplete, client-side filtering, code validation), which is clear context beyond mere implied usage. It never states when NOT to use it or names an alternative sibling. The instruction 'Call with no parameters' conflicts with the required `q`, which undercuts the guidance at invocation time.

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