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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the authoritative NOAA data source and statutory report output, but does not disclose whether the operation is read-only, what permissions are required, whether it writes files or records, or other side-effect details.

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?

The description is a single, front-loaded sentence that identifies the action, data source, covered storm types, statutory use, and output artifacts without filler. Every phrase contributes to distinguishing the tool's purpose.

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?

The description names the generated deductions and certified Exhibit S reports, but with no output schema and no annotations, it does not fully explain return values, operational behavior, or when this tool should be preferred over related audit siblings. The schema covers inputs well, but contextual gaps remain for a complex statutory and weather-analysis 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 description coverage is 100%, so the input schema already explains all five parameters, including county, format, address, parcel_id, and assessed_improvement_value. The description does not add meaningful semantics beyond the schema for any parameter.

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 and resource: auditing a parcel against authoritative NOAA severe weather storm swaths, including hail, tornado, hurricane wind, and flash flood. It also names the statutory purpose and output artifacts, which distinguishes it from sibling audit tools such as FEMA flood hazard or general property tax audits.

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 intended use is implied by the purpose: generating statutory casualty loss assessment deductions and certified Exhibit S reports under T.C.A. § 67-5-603. However, the description does not explicitly state when to use this tool versus related siblings such as audit_fema_flood_hazard, nor does it provide exclusions or prerequisites.

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