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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context that alerts are active and NWS-sourced, but it does not disclose return format, alert severity, or any NWS-specific behavior. This is adequate but not rich.

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 short sentences, front-loaded with the core purpose, and every phrase adds value. There is no filler or repetition of the title.

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?

The description gives the essential resource and query modes but does not clarify requiredness or exclusivity of parameters, and there is no output schema to inform the agent about the response. Since all four parameters are optional in the schema, an agent could easily invoke the tool incorrectly by providing no query or combining incompatible parameters.

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 only 25% (only 'state' has a description), and the description partially compensates by clarifying that lat+lon are used together, zip_code is a US ZIP, and state is a two-letter code. However, it leaves ambiguity about whether the parameters are mutually exclusive, whether at least one is required, and what lat/lon ranges are expected.

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 identifies the tool's output as active weather alerts from the US National Weather Service, and 'Query' supplies a specific verb. It also distinguishes weather_alerts from sibling weather tools like weather_current, weather_forecast, and weather_air_quality by focusing on active advisories/warnings.

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?

No guidance is given on when to choose this tool over related weather siblings, and no alternatives or exclusions are named. The description only states what query parameters are accepted, not the use case or how to decide between weather_alerts and tools like weather_forecast or weather_current.

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