srgssr_weather_forecast_7day

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

Annotations already declare this as read-only and idempotent. The description adds useful behavioral context: only for Swiss locations, maximum 7 days, and reliability decreases for days 5-7. 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 concise and well-structured using tags for use_case and important_notes. It front-loads the core functionality and includes a relevant example. No superfluous content.

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's complexity (7-day forecast) and the existence of an output schema, the description covers location scope, reliability, and use cases adequately. The output schema likely explains the return format, so no additional description 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 description coverage is 0% per context, so the description must compensate. It provides an example (latitude=47.3769, longitude=8.5417) but does not explain the geolocation_id parameter or the coordinate ranges. Baseline 3 is appropriate given the lack of detail.

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 provides a 7-day weather forecast with min/max temperature, precipitation, and weather conditions. It distinguishes from sibling tools like srgssr_weather_current and srgssr_weather_forecast_24h by specifying the 7-day timeframe.

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?

Includes explicit use cases (weekly planning, tourism recommendations, trend analysis) and important notes (Swiss locations only, days 1-3 more reliable). Lacks explicit alternatives or when-not-to-use, but the sibling tools cover different timeframes implicitly.

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