Corporate-account or group-booking enquiry, routed to the Travellers Group corporate team. Requires guest consent, as with create_enquiry.
| Name | Required | Description | Default |
|---|---|---|---|
| company | Yes | ||
| contact | Yes | ||
| context_summary | Yes | ||
| consent_confirmed | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds consent requirement and routing information beyond annotations, but does not detail response, side effects, or failure modes. Annotations already mark as non-read-only, so description provides modest added 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?
Two concise sentences, front-loaded with purpose and key requirement. No fluff, but could be more detailed given parameter count.
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?
Fails to cover required parameters, nested object structure, output expectations, or failure behavior. Underwhelming for a 4-param tool with no output schema.
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, description should explain required parameters. It only touches on consent_confirmed, leaving company, contact, and context_summary unexplained. This is a significant gap.
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 creates a corporate-account or group-booking enquiry routed to the corporate team, distinguishing it from sibling create_enquiry for regular enquiries.
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?
Implies use for corporate/group bookings, with mention of consent requirement. Does not explicitly state when not to use, but the context of sibling tools and 'corporate' qualifier provides clear guidance.
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.
