fa_search_flights

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

Annotations declare readOnlyHint and openWorldHint. Description explains query syntax but does not add context on pagination, rate limits, or exactly what 'airborne flights' means. Minimal additional behavioral disclosure.

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?

Concise two sentences plus list and example. No wasted words, but structure could be slightly improved (e.g., use bullet points for keys). Efficient overall.

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?

With 3 params and no output schema, description covers query syntax well but omits pagination behavior, return format, and exact scope ('airborne flights' not elaborated). Sufficient but not fully comprehensive.

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 100%, but description greatly enhances the query parameter by detailing the -key value syntax, listing all keys, and providing an example. This goes well beyond the schema's minimal description.

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?

Clearly states 'Search airborne flights using AeroAPI's simplified query syntax'. Verb and resource are specific. Distinguishes from siblings like fa_search_flights_advanced which likely uses a different 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?

Provides explicit usage guidance: query syntax with keys and example. However, does not explicitly state when not to use or compare to alternatives like fa_search_flights_advanced.

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