fema_disaster_declarations

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

Annotations declare readOnlyHint=true; description adds return fields and temporal coverage without contradiction. However, it does not disclose pagination behavior or result limits beyond the schema's top/skip parameters.

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 concise sentences, roughly 20 words, front-loaded with verb+resource. Every sentence adds value—no 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?

No output schema, so mentioning return fields (name, type, area, programs) helps. Parameter schema handles filter definitions. Missing explicit pagination/limits, but adequate for a straightforward search 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?

Schema covers 100% of parameters with individual descriptions; description only names a subset of filter fields already present in schema, adding no additional semantic depth.

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?

Description uses specific verb 'Search' and resource 'FEMA disaster declarations', includes temporal scope 'since 1953', and clearly distinguishes from sibling FEMA tools like fema_housing_assistance and fema_public_assistance.

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?

States supported filters (state, year, incident type, declaration type) and return fields, giving clear context for when to use. Does not explicitly name alternatives or exclusions, but the context is sufficient for a search tool.

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