search_hotels

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

Annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=true) already indicate safety. Description adds critical context: 'Guests pay the hotel directly... not through a third party', 'Loyalty points always apply', and that chain_code is a backend filter. No contradiction with annotations.

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?

Well-structured with clear paragraphs: purpose, when-to-use, payment model, chain_code note, next steps. However, slightly verbose with examples and brand list; could be more concise.

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?

No output schema, but description does not describe return format. Given 13 parameters and missing output schema, some description of response structure would help completeness. However, the description covers usage well.

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. Description adds value by explaining chain_code mapping, pagination parameters (search_id, cursor), and domain-specific constraints (e.g., 'chain_code is a backend filter — never surface'). This goes beyond 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 the tool's purpose as searching hotels worldwide by location and dates. It specifies verb (search), resource (hotels), and scope (worldwide). Differentiates from sibling tools like get_hotel_details and book_hotel by outlining the workflow.

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?

Explicit when-to-use guidance: 'Always search when the user mentions hotels... Never skip search.' Also provides post-search workflow: 'Next step: get_hotel_details... then book_hotel.' Includes mappings for chain_code to brand names and cautions not to surface chain_code to guests.

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