get_forecast

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

With no annotations, the description carries the full burden. It discloses the 16-day limit but fails to explain how location is specified (city name vs. coordinates), whether the tool is read-only, or any error/return behavior. This is insufficient for a tool with four optional parameters.

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, front-loaded sentence with no wasted words. It efficiently communicates the core function and a key constraint.

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 has four optional parameters and sibling tools that target similar functionality, the description is too sparse. It does not clarify how to select a location (city vs. coordinates), what happens if both are provided, or how this differs from get_weather/get_hourly_forecast. The lack of an output schema makes this gap more significant.

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 provides 100% coverage with descriptions for all four parameters, so the baseline is 3. The description adds no additional meaning about parameter usage or precedence, simply repeating the day limit already present in 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 the tool gets a weather forecast for a location, with an explicit 16-day limit. It distinguishes from siblings like get_hourly_forecast by focusing on the forecast aspect, though it doesn't differentiate explicitly from get_weather.

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 provided on when to use this tool versus alternatives like get_hourly_forecast or get_weather. The description does not mention any exclusions, prerequisites, or situational context.

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