get_property_sectionRetrieve one complete owner-attested public knowledge section by the exact ID returned from search_property_knowledge.
| Name | Required | Description | Default |
|---|---|---|---|
| section_id | Yes | An allowlisted public section ID. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the behavioral trait 'owner-attested' and 'complete' section, which conveys authenticity and scope. It does not mention error behavior for invalid IDs, but the schema's enum restricts valid inputs, making that less critical. This is more than the baseline but not exhaustive.
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 a single, well-structured sentence that front-loads the verb 'Retrieve' and immediately states the resource and the parameter provenance. There is zero redundancy, and every word contributes to understanding the tool's function.
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 tool with one parameter, an output-free description, and strong annotations (readOnly, idempotent, non-destructive), the description is complete. It tells the agent what the tool does, where the input comes from, and the nature of the returned data. No additional information is necessary for correct invocation.
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 coverage is 100% (the enum fully defines valid IDs). The description adds meaning beyond the schema by stating the ID must be 'the exact ID returned from search_property_knowledge,' which clarifies how to obtain the parameter and emphasizes exactness. This is valuable context that the schema alone does not provide.
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 verb ('Retrieve') and resource ('one complete owner-attested public knowledge section'), and distinguishes itself from the sibling tool search_property_knowledge by specifying 'by the exact ID returned from search_property_knowledge.' This makes the tool's purpose unambiguous and correctly differentiated.
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 explicitly tells the agent when to use this tool: it requires an exact ID returned from search_property_knowledge. This names the alternative tool and sets a clear precondition, effectively guiding the agent to use search first and this tool as a follow-up for retrieving a specific complete section.
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.