get_ski_area_detailReturn public ski area information, facts, images, ski maps and related ski resorts. Use this for destination context and recommendations, not for apartment prices or availability; use search_apartments for live week-specific accommodation results.
| Name | Required | Description | Default |
|---|---|---|---|
| skiAreaId | Yes | Ski area id from list_ski_areas. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already mark this as read-only, idempotent, and non-destructive. The description adds that the data is public and describes the content categories returned (facts, images, ski maps, related resorts), giving some behavioral context beyond the safety profile, though it does not discuss pagination, rate limits, or auth.
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 main purpose, and includes a clear exclusion and alternative. No wasted words, and it efficiently conveys the tool's scope and usage.
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 detail tool with one parameter, no output schema, and strong annotations, the description provides sufficient information about what is returned and when to use it. It lacks explicit distinction from get_ski_resort_detail but is otherwise complete for a single-resource detail endpoint.
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 schema already provides full coverage for the single parameter, describing it as a ski area id from list_ski_areas. The description does not add any additional parameter semantics, so with 100% schema coverage the baseline of 3 applies.
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 explicitly states it returns public ski area information, facts, images, ski maps, and related ski resorts, with a clear verb and resource. It also differentiates from search_apartments by noting it is not for apartment prices or availability, helping distinguish from a sibling.
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 provides explicit usage guidance: use for destination context and recommendations, not for apartment prices, and names search_apartments as the alternative for live week-specific accommodation results. This clearly indicates when to use the tool versus an alternative.
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: separate tools for different entity details (accommodation, ski area, resort), distinct search vs. list operations, and specialized tools for ski pass prices and search vocabulary. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_accommodation_detail, list_ski_areas, search_apartments). Verbs are appropriately chosen (get, list, search, resolve), and there are no mixed conventions.
With 10 tools covering destination discovery, accommodation details, apartment search, pricing, and search utilities, the count is well-scoped for a ski accommodation search domain. No unnecessary tools or missing essentials.
The tool set covers the full user journey: vocabulary setup (get_search_options), keyword resolution (resolve_search_keywords), destination lists (list_ski_areas/resorts), accommodation lists (list_accommodations), detailed info (get_*_detail), apartment search with pricing (search_apartments), and ski pass pricing (get_ski_pass_prices). No obvious gaps for an information/query-focused server.