Weather Time Series

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world. The description adds behavioral details beyond annotations: date restrictions, precision limits, and location dependency. No contradictions.

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 paragraph with clear front-loading of purpose, followed by constraints and requirements. No redundant words, each sentence adds essential information.

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's complexity (8 params, 2 required, no output schema), the description covers the main use constraints and prerequisites. It does not describe output format, but the name and title imply a time series structure. An explicit return format would make it more complete.

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 100% with good descriptions. The description adds value by clarifying that at least one of location, lat+long, or ip must be provided, which is not enforced in the JSON schema. It also summarizes the precision and date constraints.

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 'Get historical weather data over a date range (time series)', which includes a specific verb and resource. It distinguishes from sibling tools like weather_current, weather_forecast, and weather_historical by emphasizing the time series aspect and date range constraints.

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 explicit constraints: max range 90 days daily, 7 days hourly; only past dates; data back to 1940; and location requirement (location, lat+long, or ip). While it does not explicitly mention when not to use or alternatives, the context is clear enough for an AI agent to decide.

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