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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that the tool does not return a price, that a human agent handles the enquiry by email within ~2 hours (up to 24 for complex trips), that seats are held together, and that names can be supplied later. This gives the agent an accurate model of the tool's asynchronous, human-mediated behavior.

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 relatively long but every sentence carries high-value information: what the tool does, what it does not do, expected response time, savings, booking benefits, required inputs, and the sibling alternative. It is front-loaded with the core purpose and contains no filler.

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?

This is a complex 20-parameter tool with no output schema and no annotations, yet the description covers the essential operational context: outcome is via email, not an immediate price; timeline; pricing benefits; and when to use a sibling tool. Nothing critical an agent needs to decide whether to call this tool is missing.

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 20 parameters thoroughly. The description adds useful workflow context around email and phone being needed for the agent to reply, but it does not materially expand the semantics of individual parameters beyond the schema.

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 and resource: it requests a quote for a group of 10 or more travellers flying together. It also distinguishes itself by explaining that this tool does NOT return a price and by naming the sibling alternative, search_flights, for smaller groups.

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?

Provides explicit when-to-use guidance: group of 10 or more, negotiated group fares. It also gives a clear exclusion and alternative: 'For 9 travellers or fewer, use search_flights instead.' The instruction to collect email and phone before calling further helps the agent invoke it correctly.

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