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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral context such as newest-first ordering, a 7-day window, and a '(Pro)' signal, but it does not explain how start/end interact with that window or mention result limits/pagination.

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 front-loads the core resource and scope with no filler. Every phrase carries useful information about the data, time window, location, ordering, or access tier.

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 simple read-only history tool, the definition covers the main purpose and annotations cover safety. However, it leaves meaningful gaps around pagination, the limit parameter, and how custom start/end values interact with the advertised 7-day window.

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 50%, with start and end documented but site and limit undocumented. The description clarifies that site is a USGS site and conveys a default 7-day window plus ordering, but it does not explain the limit parameter or how explicit start/end values relate to the stated 7-day range.

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 (gauge readings), scope (last 7 days), location constraint (USGS site), and ordering (newest first). It does not explicitly distinguish itself from the likely current-reading sibling sensors_water_gauge, 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?

The 7-day historical scope implies when the tool is useful, but there is no explicit guidance on when to choose it over sibling water tools or when not to use it. The agent must infer the intended use case from the name and time window.

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