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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the payload contents, notably that thresholds are given as stored valueCentimeters with MNW/MHW and alert marks, but says nothing about freshness of the 'current value' or rate limits.

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 dense sentence with the resource named up front followed by the field inventory. Nothing is wasted, though the parenthetical threshold detail makes it slightly list-like rather than fully front-loaded around 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?

An output schema exists, so return-value documentation is not strictly required, yet the description still summarizes the important fields and the unit convention for thresholds. Together with a fully documented single required parameter, an agent has enough to call it correctly; only station-id acquisition is left implicit.

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%, and the stationId parameter already documents both supported namespace formats (pegelonline:<uuid>, lhp:BY_10026301). The description adds no parameter-level detail, so the schema does the heavy lifting and baseline 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 verb (implicitly retrieves) and resource (master data of one station), then enumerates the returned fields: measurement type, current value with unit, thresholds, flood class, coordinates. This clearly separates it from sibling tools like search_stations (plural discovery) and get_readings (time series), though no sibling is named explicitly.

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?

Usage is only implied: 'one station' suggests a single-station lookup requiring a station id, contrasting with search_stations. There is no explicit statement of when to use this versus get_readings or get_flood_situation, nor any prerequisite guidance.

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