search_hotels

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

With no annotations, the description carries the full burden. It discloses the return content and a per-request cost ($0.01), which is useful behavioral context. However, it does not explicitly state that it is read-only (implied by 'search') or mention any rate limits or auth requirements, leaving some transparency gaps.

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 extremely concise, consisting of three short sentences that immediately state the tool's purpose, return value, and cost. There is zero wasted text and the most important 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?

The tool has 7 parameters and no output schema. The description covers the core use case but omits details about optional parameters (currency, priceRange, adults, roomQuantity) and result pagination/limits. The schema compensates for parameter semantics, but the description could be richer about expected outputs and constraints.

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?

The input schema has 100% coverage with descriptive parameter names and value examples, so the baseline is 3. The description adds only general parameter hints ('by city and dates') and does not go beyond the schema for optional parameters like currency, priceRange, or roomQuantity.

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 ('Search') and resource ('hotel offers') with key parameters ('by city and dates'), clearly distinguishing it from sibling tools like search_flights and search_locations. It also states what it returns (room details, pricing, availability), making the purpose unambiguous.

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 implicitly defines when to use the tool: when searching for hotel offers by city and date. However, it does not explicitly exclude alternatives or mention when not to use it, so it lacks explicit exclusions or alternative tool references.

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