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 only the return shape (a list) and default sort; it says nothing about pagination, result limits, auth needs, rate limits, or whether dates are required for a meaningful search.

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?

Two short, front-loaded sentences with no waste. Slightly under-specified rather than padded, so it is efficiently sized.

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?

A simple three-parameter read tool with no output schema, so the description need not explain return values in detail, but it omits any result-shape or pagination detail beyond 'a list', and the lack of date parameters vs. the search intent is left unaddressed.

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 100%, so the schema already documents departure, arrival, and the sortBy enum. The description's mention of 'sorted by price by default' merely restates what the sortBy schema description already says, adding no new parameter meaning.

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?

States a specific verb ('Search') and resource ('flights between two cities'), and adds the default ordering. However, it does nothing to distinguish itself from the sibling get_cheapest_flight, which an agent must disambiguate.

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 gives no when-to-use guidance, no indication of when to prefer get_cheapest_flight or get_flight_details, and no prerequisites (e.g., date parameters are conspicuously absent despite the schema being required to have any).

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