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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds valuable behavioral context beyond that: classification comes from source data, no own warning levels are computed, it is not an official warning, and the response ends with source/license information. It does not cover things like ordering or pagination, so 4 rather than 5.

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 purpose is front-loaded, and the text flows logically from overview to caveats to examples to output note. It is slightly long with several sentences, but each sentence contributes useful information rather than 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?

For a read-only, single-optional-parameter tool with no output schema, the description is complete: it explains what data is shown, how it is grouped, what no-data stations are included, the data provenance, the non-official-warning limitation, and the response footer. Nothing essential for correct invocation appears to be missing.

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 description coverage is 100%, so the single 'bundesland' parameter is fully documented in the schema. The description adds only an indirect example ('in Niederösterreich') and no extra syntax or semantic detail beyond the schema, making the baseline 3 appropriate.

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 states a specific resource and scope: an overview of gauge stations reporting at least elevated water flow, grouped by flood level and trend, plus stations with no data. It does not explicitly distinguish itself from siblings such as pegel_an_gewaesser or pegel_in_der_naehe, so it falls short of 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?

Example questions ('Gibt es gerade Hochwasser in Österreich?', 'Wie ist die Hochwasserlage in Niederösterreich?') make the intended usage clear. The caveat 'Keine amtliche Warnung – maßgeblich sind die Warndienste des Landes' further sets expectations. However, no sibling alternatives or explicit when-not-to-use conditions are given.

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