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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, so safety is covered; the description goes further by disclosing fail-closed inventory-schema checks, scope boundary, evidence origin, rights, and hashes. These are meaningful behavioral traits an agent needs to interpret trustworthiness, though it stops short of describing response shape or failure modes.

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?

Front-loads the returned-field inventory before the usage guidance and the exclusion, which is the right order. The field enumeration is dense and longer than strictly necessary, but every clause is informative rather than filler.

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?

There is no output schema, so the description correctly compensates by enumerating the returned metadata fields, and it supplies the trust/qualification context an agent needs for an evidence-provenance tool. Nothing essential for correct invocation is missing.

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?

With 100% schema description coverage and a single fully-documented response_format enum, the schema already carries the parameter semantics. The description adds no parameter-level detail, so baseline 3 is appropriate.

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 verb ('Return') and resource (the pinned NFHL inventory snapshot's metadata) and enumerates the exact fields returned, so the agent knows precisely what it gets. It explicitly distinguishes itself from flood_zone_lookup ('not a polygon corpus and does not replace flood_zone_lookup'), routing the agent away from a common confusion.

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?

'Use this to qualify evidence and freshness before relying on inventory results' gives explicit when-to-use guidance, and the closing sentence provides a when-not-to-use exclusion against flood_zone_lookup. It does not, however, name the actual sibling alternatives (fema_nfhl_search_inventory, get_inventory_item) that return the inventory rows themselves.

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