search_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 discloses that search results are saved internally, that all times are local and in HH:MM 24-hour format, but does not mention auth or rate limits. It is fairly transparent, but could include more about statefulness.

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 well-structured with clear sections and front-loaded purpose. It is slightly verbose but each sentence provides value, earning a 4.

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 of the nested schema and the lack of an output schema, the description adequately explains the workflow (search then retrieve options) and provides critical usage details. It is practically complete for an agent to use effectively.

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?

Although the schema_description_coverage is 0% (likely a metric artifact), the input schema has detailed descriptions for all nested properties. The tool description adds value with examples and important usage hints, going beyond what the schema provides. Baseline 3 is exceeded.

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 searches for flights using Aviasales API, provides a search_id, and saves options internally. It explicitly mentions the subsequent use of get_flight_options, distinguishing itself from its siblings.

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 provides explicit guidance on when to call this tool (as many times as needed) and when to use get_flight_options. It includes examples for one-way, round trip, multi-city, and warns against using multiple segments for alternative dates.

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