get_weather_forecast

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

No annotations are provided, and the description mentions no side effects, permissions, caching, or other behavioral details. As a read-only 'get' operation, it is likely safe, but the description does not disclose any such characteristics.

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, clear sentence with no redundant words or unnecessary details. It is concise and well-structured.

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?

The description is adequate for a simple forecast tool, but it does not mention any output format, units, or additional context that might help the agent decide among siblings. Given the presence of multiple weather-related tools, slightly more context would improve completeness.

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 schema includes 'city' (required) and 'days' (default 3) with self-explanatory names. Since schema coverage is 100%, the description adds no extra meaning beyond the names, keeping the baseline score at 3.

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 action (Get) and the resource (multi-day weather forecast for a city). The phrase 'multi-day' differentiates it from the sibling tool 'get_weather' which likely returns a single-day forecast, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus the alternatives (e.g., 'get_weather' for single-day, 'compare_weather' for comparisons). It lacks explicit conditions or usage scenarios.

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