search_multi_city

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states that 2-5 segments are supported, without mentioning error handling, performance characteristics, or what happens if constraints are violated.

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 at two sentences, but this brevity comes at the cost of missing essential details. It is not optimally informative; the second sentence adds minimal value beyond the first.

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 tool has 7 parameters, no output schema, and no annotations, the description is far from complete. It does not describe the return format, result limits beyond 'maxResults', or any ordering/filtering behavior.

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 only 14%, and the description adds no information beyond the schema's existing parameter descriptions. Key parameters like 'adults', 'cabinClass', and 'maxResults' are left unexplained, requiring the agent to infer meaning from names alone.

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 multi-city (multi-leg) flights and specifies the supported number of segments (2-5). This distinguishes it from sibling tool 'search_flights' which likely handles simpler itineraries.

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 implies use for multi-city itineraries with 2-5 segments but provides no guidance on when not to use this tool or mention of alternatives like 'search_flights' for single-leg or round-trip searches.

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