NOAA Hourly Forecast (US)

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds context: data source (NOAA), geographic restriction, and explicit output fields. No contradictions with annotations.

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 purpose, then details on output and constraints. No redundant information; every word adds value.

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 simple 2-parameter tool with an output schema and rich annotations, the description covers purpose, input requirements, output fields, temporal scope, geographic limit, and data source. No gaps identified.

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 clear descriptions for latitude and longitude (ranges provided). The description does not add new meaning beyond 'by latitude/longitude', so baseline score of 3 is appropriate.

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 retrieves hourly weather forecasts for US locations via lat/lon, specifies the time range (next 48 hours), lists returned fields (temperature, precipitation, wind), and identifies the data source (NOAA). This distinguishes it from sibling tools like noaa.weather.forecast (likely daily) and noaa.weather.observation (current conditions).

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 specifies geographic constraints (US contiguous only) and coordinate ranges, but does not explicitly guide when to use this tool versus alternatives. It implies hourly use but lacks direct comparison or exclusions.

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