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

The description adds context beyond the readOnlyHint annotation by explaining the data source (Open-Meteo Flood), update frequency ('Updates: daily'), history depth ('10y history'), and the output fields. It does not contradict any annotation and adds meaningful behavioral detail.

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 two sentences: the first explains functionality and output, the second gives explicit usage guidance and update frequency. Every clause earns its place with no redundancy, and it is front-loaded with the primary purpose.

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 listing the returned fields (flood_risk_score, peak_vs_current, peak_discharge) and explaining the underlying metric. The only minor gap is the lack of explicit units for peak_discharge, but the scale and meaning of the score are clearly stated.

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% and the single optional 'days' parameter is well documented in the schema. The description adds no additional parameter-level detail, only indirectly implying the history feature via '10y history' and 'daily' updates. This meets the baseline for full schema coverage but adds no extra value.

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 returns a 0-100 US Gulf Coast flood-risk score, with a specific calculation method (scaled peak-vs-current 7-day GloFAS river-discharge ratio) and named output fields. This specific verb+resource+scope distinguishes it from the many numbered sibling tools.

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 gives explicit usage triggers: 'Call when the user asks about Gulf Coast flooding, river discharge, rising water levels, or flood exposure' and also lists use cases like insurance loss-reserve reviews and underwriting decisions. It does not mention when not to use it or name alternatives, so it stops 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.