search_hotels

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

No annotations are provided, so the description carries the full burden. It discloses cost ($0.005 per call), payment method (USDC over x402 to x402-hotel-search), and return payload (merchant's artifact and payment receipt). It does not mention potential side effects beyond payment or failure modes, which keeps it short of a 5.

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?

Three concise, informative sentences. The first sentence states the core purpose, the second provides payment details, and the third states the return value. No filler.

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?

With no output schema, the description adequately explains the return value (merchant's artifact and payment receipt) and covers cost/payment, but does not explain how results are represented or preconditions like having a rail key. Given schema descriptions cover all parameters, this is reasonably complete.

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 the baseline is 3. The description only echoes 'city and date range' which maps to cityCode, checkIn, and checkOut, without adding syntax or details beyond the schema. No added meaning for adults or rail 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?

Description clearly states the tool searches hotel rooms and offers for a city and date range, with a specific verb ('Search') and resource, distinguishing it from sibling tools like search_flights and find_tables.

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?

It does not explicitly state when to use this over siblings or provide exclusions, but the scope ('hotel rooms and offers for a city and date range') implies the use case. No alternative tools are named, so context is clear but not explicit.

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