find_positioning_flights

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

No annotations are provided, so the description carries the full burden. It states the tool finds flights and mentions a post-verification step, but does not disclose any behavioral traits like rate limits, authentication needs, or whether results are cached. It is adequate but could add more transparency.

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 three sentences, each serving a clear purpose: state the function, explain the use case, and provide a cautionary note. It is front-loaded and wastes no 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?

With 7 parameters, 0% schema coverage, and no output schema, the description is incomplete. It does not explain return values, how to interpret results, or the meaning of parameters like `earliest_days_before` or `cabin`. An AI agent would need additional information to use this tool 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?

The schema description coverage is 0%, and the description only mentions `from_city`, `return_hub`, and `return_date` by name without explaining their formats or constraints. Parameters like `earliest_days_before`, `cabin`, `adults`, and `children` are left entirely to the schema, which is insufficient. The description should compensate by explaining these parameters.

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 it finds positioning flights from `from_city` to `return_hub` near `return_date`. It explains the context (asymmetric-return trick) and distinguishes itself from sibling tools like `search_awards` or `search_cash_one_way` by focusing on positioning flights for a specific travel pattern.

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 when to use this tool (for the asymmetric-return trick) and provides a critical guideline: candidates must be verified as refundable on the airline site before booking. It lacks explicit when-not-to-use instructions or alternatives, but the context is sufficient for an AI agent to understand its appropriate use.

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