Tier A handoff: returns a dated, pre-filled booking-engine link — LIVE availability and pricing are at that link. This tool never asserts that dates are available.
| Name | Required | Description | Default |
|---|---|---|---|
| adults | No | ||
| check_in | Yes | YYYY-MM-DD | |
| children | No | ||
| property | Yes | ||
| check_out | Yes | YYYY-MM-DD |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description clarifies that the tool never asserts availability and returns a pre-filled link, providing essential behavioral context.
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 with two sentences, front-loading the key information without any wasted words.
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 description covers the main function but omits details like the exact return format and any required authorization or rate limits, leaving some ambiguity.
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 description does not explain any parameters. With only 40% schema coverage, the agent is left uncertain about the meaning of 'property', 'adults', and 'children'.
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 it returns a booking-engine link, not direct availability, which distinguishes it from tools like get_indicative_rates. However, it does not explicitly contrast with all sibling tools.
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 lacks explicit guidance on when to use this tool versus alternatives like get_indicative_rates. The term 'Tier A handoff' is ambiguous, and there is no mention of when not to use it.
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.
Each tool has a clearly distinct purpose: availability returns a pre-filled link, enquiries are separated by type, corporate info is separate from general property info, distances vs events vs rates vs room types vs town guide vs search vs recommendation. The only potential confusion is between create_enquiry and create_corporate_enquiry, but descriptions clarify the target audience. Overall, no ambiguity.
All tool names consistently follow a verb_noun pattern in snake_case (e.g., check_availability, get_distances, create_enquiry). The verbs are appropriate (check, create, get, recommend, search) and nouns clearly indicate the resource. No mixing of styles or vague verbs.
With 12 tools, the server is well-scoped for a hotel information and enquiry system. Each tool covers a distinct aspect of the domain without overlap or unnecessary bloat. The count is within the optimal range (3-15) for an MCP server.
The tool set covers core hotel information retrieval (property, rooms, rates, distances, events, town guide) and enquiry creation (general and corporate). However, there is no tool to complete a booking or confirm availability beyond a link. This is a minor gap; agents must hand off to the booking engine. Overall, the surface is mostly complete for its stated purpose.
