compare_destinations

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

The description mentions throttling ('one search per destination (throttled)'), which is a key behavioral trait. However, with no annotations provided, it does not disclose other behaviors such as data freshness, authentication needs, or rate limits beyond throttling.

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 concise with a clear one-sentence purpose, followed by a well-structured list of all parameters. No unnecessary words; every sentence adds value.

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 (11 parameters, output schema present), the description covers the core purpose, parameter details, and a key behavioral note (throttling). It does not explain return value formatting or error handling, but the output schema may cover that. Overall, it is largely complete.

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 description provides brief explanations for all 11 parameters, compensating for the 0% schema description coverage. Examples include 'Comma-separated IATA destination codes' for to_airports and 'Departure date YYYY-MM-DD' for departure_date. However, some parameters like 'seat' lack allowed values or further detail.

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 compares cheapest price to several destinations from same departure airports, specifically mentioning 'where can we go cheaply inspiration searches'. This distinguishes it from siblings like search_flights which are for specific routes.

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 indicates when to use: for inspiration searches across multiple destinations. It notes 'one search per destination (throttled)', implying it's suitable when throttling is acceptable. However, it does not explicitly state when NOT to use compared to other tools like search_flights or search_flexible_dates.

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