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

Annotations already declare a safe idempotent read, but the description adds real value beyond them: it is a 'complete pinned projection' (snapshot semantics), returns bounded pagination, both displayed and filename-derived dates, and snapshot hashes, and is explicitly 'inventory metadata only'. This return-shape disclosure is substantial for a tool with no output schema.

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-loaded purpose followed by return contents and a routing note; every sentence carries information. It is slightly dense with internal jargon ('LiveDataLink's complete pinned projection', 'canonical FEMA download evidence') but not padded.

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 an 11-parameter, no-required, no-output-schema tool the description is complete enough to invoke correctly: it names the filter dimensions, the snapshot/pinning nature, the returned artifacts, the metadata-only limitation, and the alternative for point flood-zone queries. Nothing an agent needs to call it 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?

Schema description coverage is 100% and every parameter carries its own description, so the schema does the heavy lifting. The description restates the filter axes (jurisdiction, state, unit kind, update date, advertised ZIP size) without adding syntax or semantics beyond the schema; 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 verb+resource (search FEMA's NFHL coverage/download inventory) and enumerates the filterable dimensions, so the agent knows exactly what the tool returns. It differentiates from flood_zone_lookup, but does not distinguish itself from its nearest siblings (fema_nfhl_get_inventory_item, fema_nfhl_compare_inventory_items, fema_nfhl_summarize_state_inventory), which share the same resource.

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?

Gives explicit usage context ('screen coverage/freshness and plan acquisition before property diligence') and names an alternative with its selecting condition ('for an address or coordinate flood-zone question use flood_zone_lookup'). No exclusion guidance against the other NFHL inventory siblings, but the when-to-use framing is clear.

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