fema-nri-county-risk-profile

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

The description mentions that it reads live from the official government source, which is a behavioral trait. However, it does not disclose other behaviors like rate limiting, error handling, fallback mechanisms (e.g., tract-to-county fallback is only in parameter docs), or any side effects. Since no annotations are provided, the description carries the transparency burden but only partially satisfies it.

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?

The description is a single, well-structured paragraph that front-loads the main purpose and then lists key outputs. It is concise, avoids redundancy with the schema, and effectively communicates the tool's value without unnecessary detail.

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?

Given the tool's moderate complexity and the absence of an output schema, the description adequately covers the primary return values and the general use case. It does not delve into edge cases or limitations, but these are partially addressed in parameter descriptions. Overall, it provides sufficient context for an agent to understand when and how to use the tool.

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?

The tool description does not add any semantic information about parameters beyond what the input schema already provides. The schema descriptions are thorough (covering all parameters, defaults, and fallbacks), so the description does not need to repeat them. Given the high schema coverage, a baseline of 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?

The description clearly states the tool's core function: joining assets to FEMA's National Risk Index hazard profile, and enumerates the specific outputs (composite risk score, expected annual loss, social vulnerability, resilience, top-3 hazards). It also distinguishes itself from sibling tools by focusing on risk profiles and supporting multiple asset inputs. The reference to the store page reinforces its identity.

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?

The description does not provide any explicit guidance on when to use this tool versus alternative environmental screening tools, nor does it mention conditions that would favor this tool. While the purpose implies a scenario (e.g., needing FEMA risk data), no concrete usage criteria or exclusions are stated.

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