get_daily_forecast

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

With no annotations, the description fully bears the transparency burden. It discloses the Open-Meteo data source, 1–16 day range, clamping behavior, precedence of date range over days, and default end_date behavior, providing rich context beyond the schema.

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 well-structured with a front-loaded purpose statement followed by a concise parameter list. Every sentence adds meaningful information, and the format is scannable without unnecessary verbosity.

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?

Despite the absence of annotations and schema descriptions, the description covers all essential aspects: what data is returned, how to specify the period, parameter interactions, and even a note about geocoding. With an output schema available, this is complete for effective tool invocation.

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 has zero descriptions, but the description thoroughly explains each parameter with examples, defaults, clamping, and mutual exclusion details. This fully compensates for the missing schema documentation.

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 a multi-day weather forecast for a location', which clearly states the action and resource. It further specifies daily highs/lows, precipitation, and wind, distinguishing it from current and hourly forecast siblings.

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 guidance on when to use the days parameter versus start_date/end_date, and explicitly instructs calling GetDateTime for named periods. However, it does not explicitly mention when not to use this tool (e.g., for hourly or current conditions), leaving out direct sibling differentiation.

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