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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the sort order ('sorted by flight count descending') and the returned fields (city and country info), which is useful context beyond the annotations. It does not disclose the default limit of 20, the 100 cap, or how the date window affects the ranking, which are relevant behavioral facts.

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?

Four short sentences ordered sensibly: purpose, filter dimensions, the bidirectional switch, return shape, then an example. The example partially restates what the second sentence already says, but nothing is egregiously padded.

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 return-shape sentence is a bonus rather than a requirement, and the read-only nature is covered by annotations. However, for a tool with 8 parameters where two are date bounds, omitting any description of the time window leaves a real gap in what an agent needs to call it correctly.

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 only 13%, so the description must carry most of the load. It explains the country/airport filters and re-explains bidirectional (already documented in the schema), but dateFrom and dateTo — likely the most consequential parameters for a frequency ranking — and limit are never mentioned in either place.

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 and metric — 'Top flight routes ranked by frequency' — with the filtering dimensions named immediately after. It is distinguishable from siblings like Flight_flights_by_country or Flight_flights_by_distance by being route-centric, though it never explicitly contrasts itself with them.

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?

Gives a concrete worked example ('departureCountry=AU, arrivalCountry=ID, bidirectional=true') that shows exactly how to compose the filters for the intended use case. It stops short of naming alternatives or stating when another tool is preferable, so no exclusions are provided.

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