fa_search_flights

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

Annotations 'readOnlyHint: true' and 'openWorldHint: true' are present. The description adds context about billing (capped at 20 pages) and query string limits (1000 bytes), going beyond the annotations.

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 a single paragraph that concisely explains the tool's purpose, syntax, and example. Every sentence adds value, with no unnecessary words.

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?

While there is no output schema, the description covers pagination via cursor and max_pages. It lacks details on response structure, but given the tool's simplicity and the presence of sibling tools for more detailed flight data, this is acceptable.

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 covers all parameters with descriptions (100% coverage). The description adds significant meaning by explaining the query syntax, listing valid keys, and providing an example. It also clarifies the billing implication for max_pages.

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 clearly states 'Search airborne flights using AeroAPI's simplified query syntax', specifying both the resource and method. It distinguishes itself from the sibling 'fa_search_flights_advanced' by emphasizing the simplified syntax.

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 description explains the query syntax and provides an example, making it clear when to use this tool for simple queries. However, it does not explicitly state when not to use it (e.g., for complex queries, use the advanced version).

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