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

The annotations already mark this as read-only and open-world. The description adds useful context beyond that: single-hotel scope, date-range dependence, the offerRef output contract, and the refresh-before-checkout rationale. It doesn't mention pagination or limits, but that is a minor gap given the annotations.

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?

Three sentences with no filler: purpose first, then workflow linkage, then when-to-call. Every sentence earns its place and the most decision-relevant information is front-loaded.

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?

For an 8-parameter tool with no output schema, the description is reasonably complete: it tells the agent where to get the ref, what date range to use, and what to do with the returned offerRef. Minor gaps remain: the return shape is only partially described and the required hotel-identifier constraint is not made explicit.

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 baseline is 3. The description reinforces the source of ref and the date range, but it adds little parameter meaning beyond what the schema already provides. It also does not explicitly clarify that a hotel identifier (ref, supplierCode, or supplierHotelId) is needed despite only checkIn/checkOut being marked required.

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 uses a specific verb ('List'), a specific resource ('bookable rooms'), and explicit scoping ('ONE hotel and date range'). It also distinguishes this tool from siblings by explaining that the returned offerRef feeds into get_checkout_quote/create_checkout.

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?

It clearly says to use the hotel ref from search_hotels or search and when to call: to see all of a chosen hotel's rooms or refresh availability before checkout. It names downstream tools, though it doesn't explicitly state when not to use this tool versus get_hotel_details.

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