spc_storm_reports

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

No annotations are provided, so the description carries the full behavioral burden. 'Today's' usefully discloses temporal scope (current-day only, not historical), but it says nothing about refresh cadence, data provenance, whether reporting is preliminary, or access constraints for a read-style tool.

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?

One tight, front-loaded sentence with zero filler. It is appropriately sized, though space that could have documented the 'detail' parameter is unused.

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?

An output schema exists so return values need not be explained, and the hazard coverage is stated. However, the unexplained 'detail' parameter and the absence of any routing guidance versus similar weather/disaster siblings leave meaningful gaps for an agent deciding when and how to call it.

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?

The single 'detail' parameter has 0% schema coverage and no description in the text, so the agent cannot tell what values it accepts or what 'short' means versus alternatives. With one undocumented param the description needed to compensate and does not.

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?

States a specific verb+resource: 'Today's SPC severe weather reports' with the covered hazard types spelled out (tornado, wind, hail). An agent immediately knows what data this retrieves, though it doesn't distinguish itself from nearby siblings like disaster_alerts or weather_sondes.

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 on when to use this versus the many adjacent weather/disaster tools (disaster_alerts, tropical_cyclones, climate_anomalies). Nothing tells the agent whether this is real-time-only, if it supplements or duplicates those siblings, or any prerequisite conditions.

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