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

Annotations cover safety (readOnlyHint=true, idempotentHint=true, non-destructive), so the bar is lower. The description adds value beyond annotations by flagging that valid_time is event occurrence in UTC and should be cited locally, and by characterizing reports as 'verified' — a meaningful data-quality trait. No contradiction 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?

Four sentences, each earning its place: definition, use case, time-zone caveat, and a concrete example. The core definition is front-loaded and the example is compact and illustrative without bloat.

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?

With a rich output schema and strong annotations, the description correctly focuses on what structure cannot convey: the UTC time semantics and the tool's evidentiary role for confirming severe weather. The only gap is the lack of explicit routing versus siblings such as get_alerts or get_storm_cells, which slightly weakens completeness.

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 description coverage is 100%, so all five parameters (lat, lon, type, hours, location) are already documented in structure. The description's example ('location: Wichita, hours: 12, type: H') shows composition of the params but adds no new meaning beyond the schema; 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 names a precise resource ('NWS Local Storm Reports (LSRs)') with a specific verb ('get' implied by the name but the description defines the subject matter) and enumerates the content: verified reports of tornadoes, hail, damaging winds, flooding near a location. This clearly distinguishes it from siblings like get_storm_cells (radar storm features) and get_alerts (warnings/advisories), since LSRs are a distinct NWS post-event product.

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 states an explicit use case: 'Use to confirm severe weather occurrence or assess reported damage.' This tells an agent when this tool is the right choice. It does not name alternative tools or explicit exclusions, so agents might not know to prefer get_alerts for impending warnings or get_storm_cells for active tracking.

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