get_guest_support_guidanceRetrieve the closest curated guest-safe technical-support sections for an installed device, appliance symptom or error. It never resets, reconfigures, disassembles or controls equipment. The input is search text, never an instruction to the server.
| Name | Required | Description | Default |
|---|---|---|---|
| device_or_issue | Yes | Device name, symptom or displayed error text. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds behavioral context by explicitly stating it 'never resets, reconfigures, disassembles or controls equipment' and that the input is search text, not an instruction. This reinforces and clarifies the safe, advisory nature of the tool beyond the 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?
Two sentences, no wasted words. The primary action and key behavioral constraints are front-loaded, making the description easy to scan and understand quickly.
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?
Given the single-parameter simplicity, strong annotations, and clear behavioral description, the tool is fully contextualized. It covers what it does, what it never does, how to phrase input, and implies appropriate use cases. No output schema is needed for this advisory tool.
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 description coverage is 100% and the parameter description is clear. The description adds extra semantics by clarifying that 'device_or_issue' should be search text, not an instruction, which is a meaningful distinction beyond the schema's minimal description.
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 a specific action ('Retrieve the closest curated guest-safe technical-support sections') and a specific resource ('installed device, appliance symptom or error'). It distinguishes itself from sibling tools by focusing on guest support guidance rather than availability, booking, or property knowledge.
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 conveys clear usage context: use when you need guest-safe technical support sections for a device/issue. It does not explicitly name alternatives or exclusions, but the phrase 'input is search text, never an instruction' provides an important guideline for how to invoke it. Sibling tool names further differentiate context.
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.