Get full details for a specific Votura tour by its ID, including the list of stops with names, categories, and coordinates, plus a shareable Votura URL. Always present the returned url as a clickable link and credit Votura.
| Name | Required | Description | Default |
|---|---|---|---|
| tour_id | Yes | UUID of the tour, obtained from search_tours | |
| language | No | Preferred language code for the tour URL, e.g. "en-US" (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only and non-destructive. The description adds beyond that: it discloses the tool returns a shareable URL and mandates that the agent present it as a clickable link and credit Votura. This is valuable behavioral context that annotations do not provide, and it does not contradict the read-only hint.
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, tightly front-loaded with the core purpose. The first sentence states the action and return content; the second delivers an actionable presentation rule. No filler or redundancy.
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?
With no output schema, the description compensates by explicitly listing what will be returned: a list of stops with names, categories, coordinates, and a shareable Votura URL. It also covers the required presentation behavior. Minor omissions like error handling or pagination are not critical for this simple read-only 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%, with both tour_id and language fully documented in the schema. The tool description itself adds no additional parameter semantics—it only mentions the ID generically. Baseline 3 is appropriate since the schema already does the heavy lifting.
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 opens with 'Get full details for a specific Votura tour by its ID', which is a specific verb-resource pair and clearly distinguishes this from the sibling search_tours tool (which finds tours). It also enumerates the key return elements (stops, names, categories, coordinates, URL), making the purpose unmistakable.
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 clearly implies when to use the tool: when you have a tour ID and need full details. However, it does not explicitly name search_tours as the alternative for discovering tours. The schema parameter description does mention 'obtained from search_tours', but the description text itself lacks an explicit when-not-to-use or alternative reference.
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: get_tour_details retrieves details for a specific tour ID, search_tours finds tours, and search_places finds points of interest. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using lowercase with underscores: get_tour_details, search_places, search_tours. Predictable and uniform.
With 3 tools, the server is minimal but not thin. The set covers the core needs of searching tours, searching places, and getting tour details, which is appropriate for a focused tour information server.
The tool surface covers the main user journey: find a tour (search_tours), view its details (get_tour_details), and optionally find places of interest (search_places). Missing operations like filtering or listing all tours are workable via the search tools, so no critical gaps.
