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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuine domain behavior beyond the annotations: only stations with an active flood class are returned, and the 1–4 class scale is defined. It stops short of describing result volume or ordering.

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?

A single compact sentence with the core purpose front-loaded and the optional filter trailing. No filler, and the parenthetical class scale earns its space by defining the key domain concept.

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 an output schema present, return values need no explanation, and the optional parameter is covered. The only gap is that the acronym 'LHP' is left unexplained and it is not stated what an unfiltered call returns, though both are minor for a scope-sensitive read 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 coverage is 100% and the single optional parameter is fully documented in the schema (ISO 3166-2 code). The description only restates that state filtering is optional, adding no syntax or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific resource (current flood situation) and scope (stations with an active LHP flood class), which is concrete enough for an agent to act on. It implicitly contrasts with the forecast sibling by emphasizing 'current', but it does not explicitly differentiate itself from get_forecast, get_readings, or search_stations.

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?

'Current' and 'optionally per federal state' imply when this tool is appropriate (real-time status, optional regional narrowing), but there is no explicit statement of when to prefer it over get_forecast or get_readings, nor any exclusion or prerequisite.

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