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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond that: unit conventions (ft, kt, s, F, mi; directions FROM), the fact that source/freshness metadata is returned, and the safety caveat about empty reports not implying safe conditions.

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 tight sentences, front-loaded with what the tool returns; the units clause is dense but efficient. Minor redundancy between the title and the opening sentence, but nothing is wasted.

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 usefully states that data plus source/freshness metadata come back, and it documents units. However, the bbox/category filtering of the nested query object goes unexplained, leaving the calling contract incomplete for a spatial query 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 description coverage is 0%, and the single nested query object carries undocumented bbox and category filters. The description says nothing about either, so it fails to compensate for the coverage gap even though the units note adds context.

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?

It names a specific resource (Florida NOAA river and water gauges) and its content (observed readings plus separate forecast summaries), so an agent knows exactly what dataset this returns. It is distinguishable in domain from siblings like get_florida_lakes and get_usgs_water, though it never explicitly contrasts itself with them.

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?

There is no statement of when to call this versus alternatives such as get_usgs_water, get_florida_lakes, or get_forecast, and no prerequisites. The only guidance-like sentence is an interpretive caveat ('Empty reports do not establish safe conditions'), which is not a usage routing rule.

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