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 default forecast length and data source, but omits location resolution behavior, units assumptions, whether coordinates and query are alternative inputs, and what happens if no location is supplied.

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 sentence with no filler. It conveys the core purpose, source, and default behavior efficiently, even though it could be more informative.

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?

Without an output schema or annotations, the description leaves important gaps: how location is specified, which parameters are expected, whether units default to metric, and what the returned forecast contains. The agent is not equipped to decide between this and the dashboard or hourly tools from the description alone.

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 80%, so parameters are mostly documented there. The description adds the default value of 10 for 'days', which is not in the schema, but it does not clarify the relationship between query and latitude/longitude or the units default.

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 provides a daily forecast from the Google Weather API and notes the default 10-day window. The 'daily' scope distinguishes it from current and hourly forecast siblings, though it does not explicitly name or contrast alternatives.

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?

No guidance is given for when to use this tool versus get_current_weather, get_hourly_forecast, or get_weather_dashboard. The only implicit signal is 'daily' in the description; there are no explicit when-to-use conditions or exclusions.

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