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

Annotations already cover read-only, open-world, non-idempotent and non-destructive behavior, so the bar is lower. The description adds genuinely useful context: tonight is resolved in the hotel time zone, provider links open external booking pages with no reservation, a unique hotel match is required, and session inheritance preserves device and filters. However these points are restated repeatedly rather than expanded, so the marginal disclosure is thinner than the length suggests.

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?

Purpose is front-loaded, but the text is roughly twice the necessary length and loops: the 'all room groups are in the first response / do not paginate / do not re-query' point is made four or five separate times, and the hotel_id/hotel_name rule is stated twice. Sizeable chunks exist to repeat, not to add information.

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 18-parameter, nested, annotation-light tool with no output schema, this covers the essential decision inputs — date sourcing, hotel identification, session inheritance, and the shape of the return (room_groups, rate terms, provider minimums, raw_offer_page meaning). Gaps remain on occupancy/rooms and provider filtering, but nothing that would cause a wrong call.

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 coverage is 61%, so the schema carries much of the load and a 3 baseline applies. The description clarifies the highest-risk parameters — hotel_id vs hotel_name exclusivity, destination as disambiguator, date_intent tonight, and full inheritance semantics for search_quote_session_id — but says nothing about providers, rooms/occupancy structure, region/country vs residency_country, or breakfast_included.

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?

Opens with a specific verb and resource — 'Get one identified or named hotel's room options and provider prices' — scoped to hotel-local dates or date_intent: tonight. It also explicitly partitions work against both siblings, routing undated amenities/policies to get_hotel and implying search_hotels as the source of the hotel_id.

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?

Gives concrete selection rules: supply exactly one of hotel_id or hotel_name, supply check_in/check_out, date_intent, or search_quote_session_id, use destination only for disambiguation, and ask only when the hotel is ambiguous. It also names the alternative tool for hotel facts and forbids redundant destination re-searches.

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