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 data source (Open-Meteo), hourly granularity, up to 16 days, and wind speed units. This gives a good understanding of output characteristics, though it does not mention idempotency or error handling.

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?

Three sentences with no wasted words. The first sentence states the core function, the second the data source, and the third provides specific output details. Well-structured and front-loaded.

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 3 well-documented parameters and no output schema, the description covers key aspects: time range, data source, and wind speed units. It could be more detailed about other forecast elements (e.g., temperature), but it is sufficient for selection.

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?

All parameters (lat, lon, days) have descriptions in the input schema, so baseline is 3. The description adds context about wind speed units but does not enhance parameter understanding beyond 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 retrieves hourly wind and weather forecasts for up to 16 days. The mention of 'Uses Open-Meteo' and the specific wind speed units differentiates it from sibling tools like get_live_measurements (current) and get_marine_forecast (marine).

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 implies usage for general wind and weather forecasting but does not explicitly state when to choose this over alternatives such as get_live_measurements or get_marine_forecast. No exclusions or context are provided.

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