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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool returns schedules, pricing, and availability, but does not disclose additional behavioral traits such as authentication requirements, rate limits, or how data freshness is handled. With annotations covering the main safety profile, the description provides modest added context.

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 consists of two concise sentences, immediately indicating the tool's action and scope. No unnecessary information or repetition.

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 9 parameters (3 required) and no output schema, the description is brief. It does not explain return value format, pagination, error behavior, or how to interpret results. The schema descriptions cover parameter syntax, but the description lacks completeness for a full understanding of tool usage.

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 all parameters. The description adds a general note about domestic/international travel and the type of data returned, but does not provide additional semantic meaning for individual parameters beyond what the schema offers.

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 the tool searches for flights between cities/airports, listing specific details like schedules, pricing, airline info, and seat availability. It distinguishes itself from sibling tools (bus_search, car_search, hotel_search) by focusing exclusively on flights.

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 flight searches but lacks explicit guidance on when to use this tool versus alternatives like bus_search or car_search. No when-not-to-use or prerequisites are mentioned.

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