Search hotels

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

With no annotations, the description carries the burden and does well by revealing that dates are automatically converted to the API's expected format and that the destination is resolved to an internal id. This adds context beyond the schema, though it doesn't describe output structure or error cases.

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 three sentences, each informative and front-loaded. It states the core purpose, then provides two key behavioral details without redundancy. No wasted words.

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 the schema covers all six parameters and the description addresses the main usage constraints (date format, destination resolution), this is complete enough for a search tool. No output schema exists, but the description's mention of 'prices and availability' gives a reasonable expectation of return values.

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 100%, so baseline is 3. The description enriches this by explaining the date format handling and automatic destination resolution, which adds meaning not present in the schema alone.

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 states 'Search hotels by destination and dates, with prices and availability,' which is a specific verb+resource+scope. It clearly distinguishes this tool from siblings like search_properties or search_products by focusing on hotels.

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 usage context: search by destination and dates, plus guidance on date format ('YYYY-MM-DD') and destination resolution. It doesn't explicitly mention when to use this tool instead of alternatives, but the hotel-specific wording implies its scope.

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