weather-alerts

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

Discloses the data source (api.weather.gov, real-time), no API key requirement, and lists return fields (event, severity, etc.). With no annotations, the description provides sufficient behavioral cues for a read-only tool. It does not mention rate limits or authentication, but these are minimal concerns for a public API.

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 focused paragraph that efficiently covers purpose, data source, filter options, return fields, and sibling relationships. It is well-structured and front-loaded with the main action, though it could be slightly more concise.

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 no output schema and moderate tool complexity, the description comprehensively covers tool behavior, input parameters, return content, data source, and relationship to the 'weather' sibling. Agents have all necessary context to invoke the tool correctly.

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%, and the description adds value by explaining that event types require exact matches, sorting by severity descending, and a default limit of 25. This extra context helps agents use parameters correctly beyond the schema definitions.

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?

Clearly states it retrieves active NOAA weather alerts for US states, listing specific event types. The description explicitly distinguishes it from the sibling 'weather' (forecasts) tool, so agents can differentiate.

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?

Explains that no API key is needed and that it can be filtered by state, event type, severity, and limit. It mentions complementing weather.js for forecasts, providing context for when to use this tool. However, it does not explicitly state when not to use it or list alternatives beyond the forecast complement.

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