dfw_nws_alerts

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

Annotations already provide safety and idempotency hints. Description adds valuable behavioral details: return fields (severity, urgency, etc.), data source (NWS api.weather.gov), and default location. No contradictions with 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?

Two sentences with no wasted words. Front-loaded with purpose and scope, then details on defaults and return fields.

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 annotations, output schema, and parameter descriptions, the description covers purpose, source, default behavior, and return fields. No gaps for a simple read-only alert tool.

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% with descriptions for all 3 params. Description adds context about defaulting to downtown Dallas and lat/lng skipping geocoding, but this is minor beyond schema.

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?

Description specifies verb 'returns', resource 'active NWS alerts', and location scope 'for a DFW location'. Lists alert types and distinguishes from sibling tools (e.g., dfw_fema_flood) by naming specific NWS alert categories.

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?

Clearly states default behavior when no address is supplied (downtown Dallas) and explains optional lat/lng parameters. Although it doesn't explicitly contrast with siblings, the tool's focus on NWS alerts is distinct enough to guide selection.

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