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 pagination behavior and the { data, total } envelope plus nested airport shape, but the output schema already documents the return, so the additional disclosure is modest.

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?

Two dense sentences, filter capabilities front-loaded, return shape second. No filler, though the filter clause packs many concepts into a comma list that is slightly hard to parse.

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 14-parameter tool with 43% schema coverage, the description covers the main filter families but leaves pagination controls and flightId unaddressed. The return-value sentence is largely redundant given the output schema exists.

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 only 43%, and the description compensates for the biggest gaps by clarifying substring-matching semantics for aircraft id / airports / cities / countries and naming sortBy/sortOrder. However it omits meaning for page, limit, flightId and icaoType, leaving several undocumented parameters untouched.

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+resource ('Paginated flight rows') and enumerates the filter dimensions, so the agent knows this is a broad, filterable listing rather than one of the aggregate siblings (stats, trends, top_routes). It stops short of naming which sibling to prefer, so it is clear but not sibling-differentiating.

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?

Usage is implied by the filter list and the note that filters are optional, giving the agent a rough sense of when to reach for it. There is no explicit 'use this instead of Flight_flights_by_country / Flight_visit_history' guidance or any exclusion criteria.

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