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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior, so the description needn't repeat safety semantics. It adds valuable operational context: the 7-day Aviationstack booking window and that out-of-window dates are refused before the API call, avoiding wasted round trips.

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?

The description is front-loaded with the tool's purpose, then required inputs, then the critical date-window constraint. Three sentences carry distinct information with no redundancy.

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?

Given the output schema and annotation coverage, the description supplies the additional context an agent needs: required parameters, return fields, and the strict 7-day date window. It is complete enough to invoke the tool correctly without over-explaining.

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%, so the schema already documents all eight parameters, including the date format and 7-day window. The description lists required parameters and return fields but adds no syntax or filtering details beyond what the schema provides, making 3 the appropriate baseline.

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 states a specific verb and resource: scheduled future flights at one airport via the /flightsFuture endpoint. It also distinguishes the result from generic flight data by emphasizing 'what flies a route on a day next week,' which helps separate it from the sibling flights tool.

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?

It clearly describes when the tool applies: future scheduled flights, requiring iataCode, type, and date, with a date within the next 7-day booking window. However, it does not explicitly name alternative sibling tools such as flights or routes for non-future flight queries.

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