weather.alerts

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

The description adds context beyond the schema, such as 'Live', 'active', and 'sorted most-severe first'. However, it lacks details on rate limits, data freshness, error handling, and response structure, which are important for a mutation tool with no 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?

The description is two sentences, front-loaded with the core purpose, and every sentence adds value. It is highly efficient with no redundant 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?

For a tool with no output schema, the description adequately covers input parameters but does not hint at the output structure (e.g., list of alerts with fields). It is somewhat incomplete for an agent to fully understand what the tool returns.

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%, so baseline is 3. The description adds meaningful context beyond the schema: explains that area includes 2-letter state or marine code, point uses 'lat,lon' decimal degrees, and results are sorted most-severe first. This helps the agent understand parameter usage.

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 live US National Weather Service active alerts (watches/warnings/advisories) for a point or area, with optional filters and sorting. It distinguishes from siblings like weather.zip by specifying the data source and type.

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 when to use the tool (for real-time severe-weather data, point or area) and mentions optional filters. It does not explicitly state when not to use it or name alternatives, but the context is clear.

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