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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description does add genuine behavioral value with the pricing model (free within the daily allowance, then $0.001 USDC via x402), which is exactly the kind of context annotations cannot carry, but it says nothing about rate limits, auth, or failure behavior for an unknown reference.

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?

Two sentences, zero waste. The content summary is front-loaded and the pricing caveat is appended where it belongs, so an agent gets the essential information in the first clause.

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 not be explained, and the description's field list plus pricing makes it callable as-is. The remaining gap is sibling disambiguation against uk-rivers__station and uk-flood__station-latest, which this crowded tool family would benefit from.

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 schema itself supplies the format example ("1491TH"), so the description need not repeat it. The description adds no syntax, casing, or lookup guidance beyond the schema, making a 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?

States a concrete resource ("one monitoring station") and enumerates the returned content (location, river, typical range, measures), so the agent knows what it retrieves. However, it does not distinguish itself from close siblings like uk-rivers__station or uk-flood__station-latest, which an agent could easily confuse it with.

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: call this when you already have a station reference and want detail. There is no explicit when-to-use, no pointer to uk-flood__river-stations or stations-near for discovering a reference, and no statement of when a sibling (station-latest for current readings) is preferable.

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