get_vansky_weatherGet VanSky vanlife weather suitability score (0-100) for a country: van_score, sleep_score, solar yield, driving conditions, awning safety, condensation risk, 7-day forecast.
| Name | Required | Description | Default |
|---|---|---|---|
| country_code | Yes | ISO 3166-1 alpha-2 country code, e.g. DE. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by detailing what the score contains (e.g., solar yield, condensation risk) and that it provides a 7-day forecast, which goes 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?
The description is a single, information-dense sentence that front-loads the key output metric (0-100 score) and lists the important sub-scores and the 7-day forecast. No redundant words or restatements.
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 tool has one required parameter, no output schema, and robust annotations, the description covers the essential aspects: what the score is, what factors are considered, and the forecast component. It is complete for an agent to decide to invoke and understand the outcome.
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 input schema provides a full description for the single parameter country_code (ISO code, maxLength 2). The description reiterates 'for a country' but adds no extra meaning beyond the schema. With 100% schema coverage, a baseline of 3 is appropriate.
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's function: getting a VanSky weather suitability score for a country, with a specific scale (0-100) and enumerated components (van_score, sleep_score, etc.). This distinguishes it from sibling tools, none of which are weather-related.
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 clear context: it is for accessing a weather suitability score for vanlife in a specified country. It does not explicitly mention when not to use it or alternatives, but given no weather-related siblings exist and the tool is straightforward, this is sufficient.
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 targeting specific resources like fuel prices, events, weather, or stories, with no overlap in functionality. For example, compare_fuel_prices and find_cheapest_fuel serve different comparison and search roles, while get_fuel_prices provides detailed data, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., compare_fuel_prices, get_currency_rate, list_events), using snake_case throughout. This predictability aids agents in understanding and selecting tools without confusion from mixed conventions.
With 11 tools, the count is well-scoped for the vanlife travel domain, covering key areas like fuel, events, weather, and stories. Each tool earns its place by addressing distinct needs, avoiding bloat while providing comprehensive coverage for planning and information retrieval.
The tool set offers strong coverage for vanlife travel, including fuel price comparison, event listings, weather suitability, and story searches, with no dead ends. A minor gap exists in lacking update or delete operations for user-specific data, but core informational and planning workflows are fully supported.