weather_forecast_hours

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only repeats the schema limit of 240 hours and fails to mention pagination (pageToken/pageSize), units, or other operational behaviors, offering minimal transparency.

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 concise sentence plus a documentation link. It is appropriately sized and front-loaded, though the link could be considered supplementary rather than essential.

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?

For a tool with 7 parameters, no annotations, and no output schema, the description is too sparse. It omits details on pagination, units, language, and response structure, making it inadequate for effective use in complex scenarios.

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%, and the description only adds value for the 'hours' parameter via the 240-hour limit. It does not explain unitsSystem, languageCode, pageToken, or pageSize, leaving most parameters semantically unexplained.

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 'up to 240 hours of hourly forecast', identifying the resource and scope. Although it lacks an explicit verb like 'get' or 'retrieve', it distinguishes from sibling tools like weather_forecast_days and weather_current_conditions by specifying 'hours'.

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 on when to use this tool versus alternatives like weather_forecast_days or weather_history_hours. The description only mentions the Google Weather API and the hour range, with no explicit context for selection.

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