get_booking_optionsReturn The Driscoll's authorised booking links and platform-specific occupancy rule. The property website does not take direct bookings or payments.
| Name | Required | Description | Default |
|---|---|---|---|
| platform | No | The intended booking platform, or unspecified when it has not yet been selected. | unspecified |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool's safe, read-only nature is covered. The description adds useful context beyond annotations, such as the platform-specific behavior and the fact that the property website does not take direct bookings or payments, which helps set expectations for the agent.
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 two sentences, front-loaded with the primary function, and includes a relevant non-obvious fact about the property website. There is no wasted wording or redundancy with schema/annotations.
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?
For a simple one-parameter, read-only tool, the description is complete. It specifies what is returned (booking links and occupancy rule) and gives a critical constraint (no direct bookings/payments). No output schema exists, but the return content is adequately summarized, and sibling differentiation is sufficient.
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 provides 100% coverage with a clear parameter description, so the description adds little beyond the schema. The 'platform-specific occupancy rule' mention relates to the platform parameter but doesn't elaborate on enum values; schema already explains them sufficiently.
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 'Return' with a clear resource: 'The Driscoll's authorised booking links and platform-specific occupancy rule.' It also adds a key differentiator from siblings by noting that 'The property website does not take direct bookings or payments,' which clarifies its unique role among booking-related 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 implies when to use the tool: whenever booking options or platform occupancy rules are needed. It provides clear context by stating the property website doesn't handle bookings directly, but it does not explicitly name alternatives or exclusions relative to sibling tools like check_stay_availability.
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 occupies a distinct domain: availability checking, booking links, guest support, and knowledge search/retrieval. There is no overlap between the search and retrieval tools, and the booking-related tools are clearly separated by function.
All tool names follow a consistent verb_noun pattern with snake_case: check_stay_availability, get_booking_options, get_guest_support_guidance, get_property_section, search_property_knowledge. The verbs are specific and the pattern is uniform across the set.
With 5 tools, the server is well-scoped for a property information and support assistant. Each tool serves a necessary function without redundancy or bloat, making the set easy to navigate.
The domain covers property knowledge search/retrieval, stay availability, booking options, and guest support—covering all apparent user needs. The search-and-retrieve pattern ensures no dead ends, and booking links substitute for direct booking as appropriate.