get_daily_forecast

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

With no annotations provided, the description carries the full burden. It discloses the output fields and parameter range (days 1-16) and default location behavior. However, it does not mention data source, update frequency, error conditions, or other behavioral traits.

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 extremely concise: two sentences contain all key information without extraneous words. It efficiently conveys purpose, output details, parameter range, default behavior, and a specific use case.

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 simplicity (2 optional params, typical forecast) and the presence of an output schema (reducing need to describe returns), the description covers essential aspects: output metrics, parameter defaults, and a usage scenario. Minor omission: no mention of concurrent location handling or error cases.

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 has 0% description coverage for parameters. The description adds meaning by specifying the allowed range for 'days' (1-16, default 7) and clarifying that 'location' defaults to 'home' and is used for travel weather. This provides context beyond the schema.

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 daily forecast with specific metrics (min/max temperature, rain sum plus probability, sunshine hours, weather condition). It distinguishes itself from siblings (get_current_weather, get_hourly_forecast) by focusing on daily aggregates over a range of days.

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 gives a clear use case ('For travel weather, set location for each road trip stop') and explains default behavior (no location = home). However, it does not explicitly state when not to use this tool compared to siblings.

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