climate.station-history

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

No annotations provided, so description bears full burden. Discloses data source, units, date range limit, and that values are measured. Does not mention rate limits, authentication, error behavior, or pagination. Adequate but incomplete.

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?

Two sentences, front-loaded with essential information. First sentence encapsulates purpose and output. Second sentence provides prerequisite. No redundant or tangential content.

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 absence of annotations and output schema, description covers key aspects: data source, measurements, units, constraints, and prerequisite. Could mention output format (JSON) or that data is daily. Mostly 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 covers all 4 parameters (100%). Description adds meaning beyond schema: context about data types (max/min/avg temp, precip, snow, wind), units (°C, mm, m/s), and the use of GHCN station IDs. Reinforces date range constraint.

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?

Description clearly states verb (get historical observations), resource (NOAA GHCN-Daily for a station), and scope (single station, date range ≤366 days, specific measurements). Distinguished from sibling climate.station-near which is for finding station IDs.

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?

Explicitly instructs to find station ID with climate.station-near first, establishing prerequisite. Implies appropriate use for historical data vs. current conditions (siblings weather.zip, weather.alerts). Could add explicit when-not-to-use.

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