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

The description adds substantial behavior beyond the readOnly/openWorld annotations: per-call price of 0.0045 USDC, the x402 payment gate, exactly what happens on an unpaid call (returns payment requirements), and the two ways to retry (X-PAYMENT/PAYMENT-SIGNATURE header or params._meta). It also discloses the attribution requirement and the professional-use disclaimer. This is exactly the kind of context annotations cannot carry.

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?

Four tight sentences, front-loaded with the resource definition followed by disclaimers and payment mechanics. Every sentence carries information, though the payment and disclaimer clauses could be trimmed slightly without losing meaning.

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 a simple two-parameter, read-only lookup with no output schema, the description covers purpose, boundaries, cost, and payment recovery. It leaves 'recent' undefined (no date range param is disclosed) and says nothing about ordering or pagination, which are the main residual gaps.

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 coverage is 100% for both parameters, so the baseline is 3 and the description does not explain state format or limit behavior beyond the schema. It does implicitly introduce a payment vector (params._meta['x402/payment']) that is not represented in the input schema, which is worth noting but is not parameter documentation per se.

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 names a specific resource and source: 'Recent official OpenFEMA v2 disaster declarations by US state, incident dates and program flags.' That is enough to separate it from siblings like place_earthquakes and place_weather_alerts. It stops short of an explicit verb such as 'list/retrieve', so it earns a 4 rather than a 5.

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?

There is a useful use-case boundary ('Statistical research/reporting only, not individual eligibility or benefit decisions') and clear guidance for the payment retry path. However, it never states when to choose this over place_earthquakes, place_weather_alerts, or usaspending_awards, and gives no prerequisites for the state parameter.

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