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

Annotations already communicate that the tool is read-only, idempotent, and non-destructive, so the description does not need to re-state safety behavior. It adds useful context by specifying 'currently-active' and listing alert categories, but it does not disclose details like result limits, geocoding behavior, or alert priority semantics.

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 entire description is one tightly packed sentence with no filler. It front-loads the core purpose and then efficiently lists alert types and input modes, which is exactly the information an agent needs.

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 read-only tool with five optional parameters and no output schema, the description gives enough context to understand what the tool returns and how to scope it. It could be slightly more explicit about whether parameters can be combined, but the 'point, state, or NWS zone' phrasing makes the likely options clear.

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?

With 60% schema description coverage, the description partially compensates by mapping query modes to parameters: 'point' implies lat/lon, 'state' maps to the state code, and 'NWS zone' maps to the zone id. The schema already describes zone, state, and location, so the description's added value is mainly clarifying that these are alternative ways to scope the request.

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 specifies a concrete resource ('National Weather Service alerts') and a clear scope ('Currently-active'), then enumerates alert types and the three supported query modes. This makes the tool easy to distinguish from nearby siblings like weather_current, weather_forecast, and disaster_declarations.

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 gives clear contextual guidance by stating that the tool covers active alerts for a point, state, or NWS zone. It does not explicitly name alternatives or state when not to use it, but the active-alert framing strongly implies its niche relative to forecast/current-condition tools.

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