gov.usgs-water

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

With no annotations, the description must fully disclose behavior. It indicates real-time data and spatial filtering but omits details on authentication, rate limits, response format, error handling, or what happens when no data is found. The minimal behavioral context is insufficient.

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 description is two concise sentences, front-loading the core action and resource. Every word serves a purpose, with no redundancy or fluff. It efficiently conveys essential information.

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?

Given five parameters, low schema coverage, and no output schema, the description adequately covers the main functionality and default parameters but lacks details on the response format, pagination, or error conditions. It is minimally viable but not fully comprehensive for an agent to use without additional context.

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?

The description adds value by explaining the default variable codes for streamflow, gage height, and water temperature, which are not fully documented in the schema. However, it does not explain the 'limit' parameter or clarify the meaning of lat/lon beyond implicit spatial context. Schema coverage is 40%, so the description partially compensates but leaves gaps.

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 clearly states the tool retrieves real-time USGS NWIS stream/river/groundwater readings within a bounding box around a given lat/lon. It specifies the data source, type of readings, and default variables, making the purpose unambiguous. No sibling tool performs a similar function, so differentiation is inherent.

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 description provides no guidance on when to use this tool versus alternatives, no exclusions, and no context about prerequisites or limitations. It simply describes what it does without addressing when it is appropriate to invoke.

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