search_cash_one_way

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

No annotations are present, so the description must fully convey behavioral traits. It only mentions 'via fli (Google Flights)' which hints at the data source but omits details on authentication, rate limits, error handling, or what happens if parameters are invalid.

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 very concise (one sentence) and front-loaded with the core purpose. It wastes no words. However, it could be slightly expanded to cover key missing aspects without becoming verbose.

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 complexity (10 parameters, no schema descriptions, no annotations), the description is insufficient. It fails to explain how to effectively use parameters like cabin, stops, hour windows, or top_n. The presence of an output schema reduces the need to describe return values, but guidance on input is lacking.

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 0%, yet the description adds no meaning to any of the 10 parameters. Parameter names like 'origin' and 'destination' are self-explanatory, but the description does not clarify format, constraints (e.g., airport codes vs city names), or how 'depart_hour_window' works.

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's a 'cash-fare one-way search via fli (Google Flights)', specifying the verb (search), resource (cash-fare one-way), and data source. This distinguishes it from the sibling tool 'search_cash_round_trip' which is for round trips.

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?

No guidance on when to use this tool vs alternatives. The description does not indicate scenarios, prerequisites, or when not to use it. Sibling tool names imply alternatives but no explicit direction is given.

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