tool_search_hotels

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

No annotations provided, so description carries full burden. It discloses data source (Google Hotels, fast_hotels) and that output includes booking deeplinks. However, it does not discuss rate limits, caching, error handling, or what happens with no results. Minimal but not misleading.

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 concise with a clear 'PLANNING' header and bullet-style parameter list. It front-loads the purpose. However, the parameter list could be more structured, but overall efficient.

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 9 parameters with no output schema and no annotations, the description adequately documents parameters but lacks behavioral context (e.g., data freshness, failure behavior, output format). The mention of 'booking deeplinks' hints at output but is insufficient for complete understanding.

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?

With 0% schema description coverage, the description adds critical meaning: examples for city (not IATA), date format YYYY-MM-DD, defaults, and format hints for price_range and ratings. It fully compensates for the missing schema descriptions.

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 clearly states 'Search hotels in a city' with a specific verb and resource. There are no sibling tools for hotel search, so it is well-distinguished.

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 mentions it uses Google Hotels names and fast_hotels plus booking deeplinks, but does not explicitly specify when to use or when not to use this tool over alternatives. Since there are no direct sibling hotel search tools, the need is lower, but still no guidance on prerequisites or exclusions.

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