get_hourly_forecast

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

No annotations are provided, so the description carries the full burden. It discloses the time range but does not explain location resolution when both location and coordinates are supplied, nor does it describe error handling, response format, or other behavioral traits. The only added value is the hour limit, which is already present in the schema's maximum constraint.

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 that is front-loaded with the verb and resource. Every word contributes to the core meaning, with no filler.

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 four optional parameters with potential ambiguity (location name vs coordinates) and no output schema, the description is not sufficient for correct invocation. It fails to specify precedence or interaction between location fields, and the sibling tool search_location suggests location naming may require resolution. The tool is relatively simple but has hidden complexity.

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 already describes all four parameters with types, ranges, and descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond re-stating the hour range; it does not clarify the relationship between location and latitude/longitude.

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's function with a specific verb and resource: 'Get hourly weather forecast for a location' and adds a precise scope (up to 384 hours / 16 days). This distinguishes it from sibling tools like get_forecast, which likely covers non-hourly forecasts.

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 does not explicitly state when to use this tool versus alternatives such as get_forecast or get_weather. The hourly scope implies use cases, but no exclusions or alternative recommendations are provided, leaving the agent to infer based on the tool name.

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