search_toolsList available 1Stay hotel booking tools. An optional keyword filters by search, book, cancel, or details; absence of a keyword returns all tools.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | No | Optional tool filter keyword, such as book, search, cancel, or details |
| Name | Required | Description | Default |
|---|---|---|---|
| tools | Yes | ||
| total | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only and non-destructive, covering the safety profile. The description adds the behavioral detail that omitting the keyword returns all tools and that the keyword filters by categories, which is not implied by the annotations alone.
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?
A single sentence that front-loads the core purpose and efficiently incorporates the parameter behavior. No wasted words; every clause earns its place.
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 is simple, with one optional parameter, and the output schema covers return values. Annotations handle safety, and the description covers usage semantics. There is no missing information an agent would need to select or invoke this tool correctly.
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 already describes the keyword parameter with examples, but the description adds the behavior when the parameter is absent ('absence of a keyword returns all tools'). This goes beyond the schema's property description and clarifies the parameter's full semantic range.
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 ('List') and resource ('available 1Stay hotel booking tools'), making it clear this is a discovery tool. It is clearly distinguished from siblings like search_hotels (which searches hotels, not tools) and operational tools like book_hotel.
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 explains the keyword filtering behavior and the default behavior without a keyword, giving agents clear guidance on invocation. It does not explicitly state when to use this tool versus alternatives, but its purpose as a tool discovery function is self-evident relative to the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools mostly map to clear stages: search_hotels, get_hotel_details, book_hotel, cancel_booking, resend_confirmation, and search_tools are all distinct. The only close pair is get_booking and lookup_booking, but their documented distinction (token/confirmation-required details vs identity-based summary lookup) prevents actual confusion.
All tools use a consistent verb_noun pattern in snake_case: search_hotels, book_hotel, cancel_booking, get_booking, lookup_booking. No mixed casing or vague names appear.
Eight tools is well-scoped for a otel booking MCP: the functional surface covers the guest journey from search to confirmation resending, and search_tools is a useful mettool. The count is neither too thin nor bloated.
The core lifecycle is present: search, rate/details, book, lookup, view details, resend confirmation, and a cancellation handoff. Missing an explicit modify/change-booking operation and cancellation requires an external page, but these are present as product constraints rather than obvious coverage gaps.