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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds meaningful behavior: exact data components, the fused verdict nature, JSON output, and cost via x402. It does not describe edge cases like handling both address and lat/lon, but the disclosed behavior goes well beyond the annotations.

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 compact and front-loaded: purpose, input mode, outputs, use cases, format, and price in two dense sentences. No filler or repeated schema content weakens it.

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 does a good job enumerating the expected result components (FEMA SFHA, county/state, conditions, alerts, verdict) and pricing. It lacks detail on exact verdict values or error behavior, but for an agent deciding whether to call and what to expect, it is largely sufficient.

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%, so the baseline is 3. The description adds value by explicitly framing 'address OR lat+lon' as an either/or choice, which the schema only implies, and by clarifying the US-property scope. This is a small but useful semantic improvement over the schema alone.

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 identifies the tool as a property site-risk bundle for US properties, combining FEMA flood-zone data, county/state, conditions, and weather alerts into a fused verdict. This distinguishes it from siblings like realestate_property_report, weather_current, and geo_location_brief by emphasizing the bundled, risk-focused output.

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?

It states explicit use cases ('For lending, insurance, diligence') and frames the tool as a one-call bundle, implying it replaces multiple separate calls. It does not name alternative tools or provide exclusion criteria, so it stops short of full routing guidance.

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