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

Annotations already indicate read-only, safe, idempotent, and open-world behavior. The description adds value by specifying the returned fields (event, severity, urgency, etc.), which is not present in annotations. No contradictions.

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?

A single, concise sentence that immediately communicates the tool's purpose, scope, and output content. No redundant or vague wording.

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 that an output schema exists, the description appropriately focuses on input (state) and high-level output fields. It provides enough context for a tool of moderate complexity, though it could briefly mention that only currently active alerts are returned.

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?

Both parameters (state, limit) have complete schema descriptions. The description does not add new meaning beyond the schema; it merely restates 'US state code' for state. Baseline 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 the tool retrieves active weather alerts for a specific US state, listing the data categories (event, severity, urgency, description, area, timing) and source (NWS/NOAA). It distinguishes from siblings like weather.alerts.active (national) and weather.alerts.get (specific alert).

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 implies use for state-level alerts but does not explicitly differentiate from similar sibling tools (weather.alerts.active, weather.alerts.get). No guidance on when to choose this over alternatives is provided.

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