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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and world-scope are covered elsewhere. The description adds the meaningful behavioral detail that results are constrained to airports valid for the destination side of a route, but says nothing about pagination, rate limits, or freshness of analytics data.

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 identifies the resource and then lists the returned data categories. No filler, no restatement of the title, nothing to trim.

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?

An output schema exists, so the description is not obligated to describe the return format, and its one-sentence summary of payload contents is a reasonable complement rather than a substitute. For a read-only lookup with fully documented parameters and annotations covering safety, this is nearly complete; the only gap is the absence of the explicit origin-side alternative for routing decisions.

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 description coverage is 100%, and the schema itself carries the substantive semantics: the locale enum's localization note, the IATA pattern with an example (MOW), and the instruction to call resolve_city_iata_code first. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

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 (returns analytics for airports usable on the destination side of a route) and enumerates the payload contents (prices, route availability, direct flights, airlines). The 'destination side' phrasing implicitly contrasts this with the sibling get_route_origin_airports_analytics, but it never names that sibling explicitly, so the differentiation is left to inference.

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 scoping phrase 'airports that can be used on the destination side of a route' implies the usage scenario for this analytics lookup, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative (e.g., the origin-side sibling). Guidance is present only by implication.

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