booking_search

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does state the core behavior ('Returns normalized Booking.com hotel search results'), but it does not explicitly confirm read-only status, mention pagination behavior via the page param, result limits, or explain what 'normalized' means. Adequate but thin for a tool with zero annotation coverage.

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 sentences, front-loaded with the primary action. There is minor redundancy: 'Search' appears in the first sentence and 'search results' in the second, and 'Booking.com hotels' is stated twice. Overall it is efficient and easy to parse.

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 a simple search tool with full schema coverage, the description is adequate but minimal. It lacks context on pagination (despite the page param), what 'normalized' results contain, and how this tool relates to sibling booking_hotel_detail for follow-up lookups. With no output schema or annotations to compensate, the description carries more weight than it fully addresses.

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 adds only 'destination and date range,' which is largely redundant with the existing schema descriptions for query, checkin, and checkout. It provides no additional meaning for the other four parameters.

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 and resource: 'Search Booking.com hotels.' It clearly differentiates from sibling tools like booking_flights_search, booking_attractions_search, and booking_hotel_detail by scoping to hotel search results. The mention of 'destination and date range' further clarifies the tool's function.

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 provides clear context for when the tool applies (searching Booking.com hotels by destination and dates), but it names no alternatives or exclusions. An agent must infer when to prefer this over similar tools like expedia_properties_search or airbnb_search, and there is no guidance on following up with booking_hotel_detail.

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