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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that it produces statutory deductions and a certified report, which is useful, but says nothing about NOAA swath coverage limits, data recency, or whether a parcel outside a swath yields a null assessment.

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 dense sentence that front-loads the action and resource before the statutory citation and outputs. Nothing is redundant, though the legal citation is placed mid-sentence where it slightly interrupts the scan.

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 five parameters, no output schema, and a closed-world annotation set, the description does state the principal outputs (deductions and an Exhibit S report), which compensates for the missing output schema. It remains thin on input-to-output mechanics, but an agent has enough to call it correctly.

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 are documented in the schema and the baseline is 3. The description adds no meaning to individual parameters, such as how assessed_improvement_value feeds the deduction calculation, leaving it at baseline.

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 states a specific verb ('Audit') and a specific resource ('parcel against authoritative NOAA severe weather storm swaths'), enumerates the hazard types (hail, tornado, hurricane wind, flash flood), and states the artifact produced (casualty loss deductions, certified Exhibit S). It does not explicitly contrast itself with the nearest sibling, audit_fema_flood_hazard, so it falls short of a 5.

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?

Usage is only implied through the statutory framing (T.C.A. § 67-5-603 casualty loss). There is no explicit when-to-use, when-not-to-use, or guidance on choosing this over audit_fema_flood_hazard for flood-related claims, which is the most likely confusion point.

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