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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful semantic context beyond annotations: that the inventory does not imply digital NFHL geometry exists everywhere and is not a flood determination. It does not add auth or rate-limit details, keeping it from 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, front-loaded with the summary contents and then the usage scope. Every clause earns its place by covering output fields, intended use, and a misuse caveat. Slightly dense but no wasted sentences.

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 enumerating the returned fields (unit counts by kind, oldest/latest package dates, total download-volume estimate, largest unit). Combined with the scope caveat, an agent has everything needed to call and interpret 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%, so both the state and response_format parameters are fully documented in the schema. The description aligns with 'one state/territory' but adds no syntax or format detail beyond what the schema already provides. 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?

Specific verb (summarize) plus resource (FEMA NFHL inventory units for one state/territory), and it enumerates exactly what the summary contains (counts by kind, package dates, download-volume estimate, largest unit). This distinguishes it from the sibling search/get/compare inventory tools without opening their schemas.

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?

Explicitly states when to use it: 'state coverage/freshness comparisons and data-acquisition budgeting.' It also guards against misuse with 'is not a flood determination.' It does not name the specific sibling tools as alternatives, so it falls short of a 5.

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