srgssr_weather_forecast_24h

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds key behavioral constraints: geographic bounding box (Swiss locations) and maximum 24 data points. No contradiction with 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 compact, using structured tags for use cases and important notes. Every sentence provides value, and the main purpose is front-loaded.

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?

The description covers purpose, usage context, constraints, and an example. With an output schema present, return values are assumed documented. Minor missing mention of authentication or data source reliability, but not critical.

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 already provides descriptions for latitude, longitude, and geolocation_id, including bounds and examples. The description's example (latitude=47.3769, longitude=8.5417) adds minimal value, resulting in baseline score.

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 it delivers hourly weather forecast for the next 24 hours from SRF Meteo. This specific verb-resource pair distinguishes it from siblings like srgssr_weather_current (current weather) and srgssr_weather_forecast_7day (7-day forecast).

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 <use_case> tag lists practical contexts (day planning, event organization, short-term warnings). The <important_notes> adds geographical and data constraints. However, it does not explicitly recommend when to use alternatives like srgssr_weather_current or srgssr_weather_forecast_7day.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.