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

With no annotations, the description carries the full burden but does disclose useful traits: the lookup is free, the source is FEMA NFIP, and the output is scoped to insured claims. It does not mention coverage limits of NFIP data, behavior for invalid/non-US ZIPs, rate limits, or whether the 'risk signal' is derived or raw.

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?

One sentence, front-loaded with the 'FREE' cost signal and then the resource, source, and return contents. No filler and nothing an agent must scroll past.

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?

For a simple single-parameter lookup with no output schema, the description adequately explains what comes back and where the data originates. It falls slightly short on input edge cases and on how the 'risk signal' should be interpreted.

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 coverage is 0% for the single 'zip' parameter, so the description must compensate. It adds real meaning by specifying a US ZIP code, but gives no format detail (5-digit vs ZIP+4) or error expectations for malformed input.

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 (insured flood-claim history), the scope (a US ZIP code), the data source (FEMA NFIP), and the returned fields (total claims, 10-year claims, risk signal). It does not differentiate itself from siblings compare_zips or flood_report, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance and no mention of the sibling tools flood_report or compare_zips, which are the obvious alternatives for related flood questions. The 'FREE' marker hints at a cost consideration but is not a routing rule.

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