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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the geographic constraint (US), the aggregation level (area rather than property), and the specific data sources composing the result (FEMA NRI, flood zone). It says nothing about behavior on unknown/unmatched locations or data freshness, which is the remaining gap.

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, front-loaded with purpose, followed immediately by the scope caveat. The enumerated output list is dense but each item is a distinct hazard/insurance dimension rather than filler, and the negative scoping line earns its place by preventing misuse.

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 carries the return-value burden and does so by naming the five result categories the caller will receive, plus the US-only and area-level constraints. What remains unstated is the shape of the response (scores vs. narrative, units) and failure behavior for unparseable locations, which keeps it from being fully complete for a two-parameter lookup.

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%, with both parameters documented in-schema including accepted location formats and the effect of property_value on dollar estimates. The description itself contributes only the word "US" as a constraint on the location parameter and does not elaborate on parameter behavior beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and resource ("Assess hazard exposure and insurance conditions for a US location") and then enumerates the concrete outputs: FEMA National Risk Index score, flood-zone coverage, mortgage flood-insurance requirement, wildfire/earthquake exposure, and local insurance-market conditions. The closing line "Describes the area, not a specific property" disambiguates it from any property-level sibling. An agent knows exactly what this returns without opening the schema.

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?

It gives a clear scope boundary (area-level, not a specific property) and a geographic restriction (US locations only), which functions as a when-not condition. It does not name an alternative tool for property-level or non-US needs, and no siblings in the list (lenders, treasury, quotes) are referenced for routing, so it stops short of full when/when-not/alternatives guidance.

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