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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly focuses on data semantics instead: the upstream source and version (FEMA OpenFEMA, NFIP Redacted Claims v3), the 2020-2024 coverage window, and the important caveat that figures are NFIP payouts rather than repair cost. It does not address data freshness, missing-state behavior, or auth, which keeps it short of a 5.

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, both load-bearing: the first front-loads scope, source and returned metrics in a compact colon list, the second carries the interpretive caveat. No filler or restatement of the title.

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 no output schema, the description compensates by naming the returned measures, and it supplies provenance, time coverage, and a semantic caveat. For a single-parameter read-only aggregate, an agent has everything needed to select and 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?

Schema description coverage is 100% for the single 'state' parameter, which already documents both accepted forms (USPS code or full name). The description adds no syntax or validation detail beyond that, so the baseline 3 applies.

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 resource (NFIP paid building claims), an explicit scope (one US state or DC, 2020-2024) and enumerates the returned metrics (paid claim count, quartiles/median of amount paid, dominant flood event and share). The state-level granularity also implicitly separates it from the sibling nfip_claims_by_county.

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 stated scope ('for one US state or DC') makes the appropriate use case clear and pairs naturally against the county-level sibling. It does not, however, explicitly say when to prefer this over nfip_claims_by_county or the other siblings, so there is no exclusion guidance.

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