weather_summary

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

With no annotations, the description fully discloses the behavior: it returns daily max/min temperature, precipitation, max wind speed, and dominant wind direction. It explains the wind direction convention (meteorological degrees) and specifies the time range (past_days back and 7 days ahead).

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 succinct with three sentences: the first states the purpose, the second details the output, and the third gives a use case. Every sentence adds value without redundancy.

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 presence of an output schema, the description adequately covers the tool's functionality, input parameters, and key details like data source. It provides sufficient context for an agent to decide when to use it.

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 coverage is 0%, but the description adds meaning by explaining the effect of 'past_days' (controls how many days back to include) and implies lat/lon are coordinates. It does not detail lat/lon format but the schema requires them.

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 it provides 'Recent and forecast weather for a point' and lists the specific fields returned (temperature, precipitation, wind speed, wind direction). It distinguishes itself from sibling tools by focusing on weather data.

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 explains that no API key is needed and notes that wind direction is important for smoke, ash, and plume dispersal questions, giving context on when to use this tool. However, it does not explicitly state alternatives or exclusions.

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