Get full details for a specific villa including description, all photos, amenities, house rules, and check-in/check-out times. Call this when the user wants more information about a property found via search_villas.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Interhome accommodation code from a search result, e.g. "IH-123456". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns full details (including specific fields). However, it does not mention idempotency, authentication requirements, or any side effects. For a read-only tool, the disclosure is adequate but not exceptional.
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 with no wasted words. The first sentence states the purpose and contents; the second provides usage context. Front-loaded and efficient.
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?
No output schema exists, so the description must cover return values. It lists key items (description, photos, amenities, house rules, times). For a simple read tool, this is fairly complete, though it could mention response structure or pagination (unlikely needed).
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%, so the schema already documents the single parameter 'code' with pattern and description. The description does not add additional meaning beyond the schema, achieving baseline 3.
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 retrieves full details for a specific villa, listing specific content (description, photos, amenities, house rules, times). It distinguishes from sibling tools like search_villas (which finds properties) and check_availability/get_quote (which serve different purposes).
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?
Explicitly tells when to use: 'when the user wants more information about a property found via search_villas.' This provides clear context for usage relative to the search flow, though it does not explicitly state when not to use.
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 serves a distinct function: search, details, availability, and quoting. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with underscores (check_availability, get_quote, get_villa_details, search_villas). No mixing of conventions.
4 tools are well-suited for a villa rental server, covering search, details, availability, and pricing without being too few or too many.
The toolset covers key operations: search, details, availability, and quotes. The only minor gap is a direct booking tool, but the provided booking link mitigates this.
