usgs_daily_water_data

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

Annotations already mark readOnlyHint=true, so the tool is read-only. The description adds that data are aggregated daily means (historical averages), which implies no real-time updates. This provides behavioral context beyond the annotations, though no additional details on rate limits or other traits are given.

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 three sentences, each serving a distinct purpose: function, differentiation, and parameter codes. No unnecessary words; information is front-loaded and efficient.

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?

While the description explains input and use case, it lacks any information about the output format, fields returned, or pagination. With no output schema, an agent lacks context on what to expect from the response, making it incomplete for a data retrieval 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 coverage is 100%, so baseline is 3. The description adds value by listing common parameter codes (00060, 00065, 00010) with their physical meanings and units, which the schema does not provide. This aids parameter selection beyond the schema descriptions.

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 verb 'Get' and resource 'USGS daily value water data (historical daily averages)'. It distinguishes from real-time instantaneous values, implying differentiation from siblings like usgs_water_data. The purpose is specific and unambiguous.

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 explicitly contrasts with real-time instantaneous values and suggests the tool is better for trend analysis. This gives clear context on when to use it, though it does not name the exact sibling tool or provide when-not-to-use conditions. Still, the guidance is effective.

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