waterpulse

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

No annotations are provided, so the description must carry the burden. It discloses per-call cost ($0.10) and endpoint coverage, but does not mention read-only behavior, authentication needs, rate limits, data freshness, or response format beyond the action parameter.

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 well-structured with a clear list of endpoints and costs, but is somewhat lengthy due to repeating the pricing symbol and endpoint names. It is front-loaded with purpose and coverage, making it easy to scan.

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 the moderate complexity (9 endpoints) and lack of output schema, the description adequately covers endpoint purposes but fails to describe return values, pagination, or error handling, leaving agents without complete guidance for invocation.

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 100%, so baseline is 3. The description lists endpoints and their context (e.g., USGS for groundwater), which adds marginal value over the parameter descriptions, but does not explain parameter relationships or usage beyond what the schema provides.

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 it is a 'global water intelligence API' and enumerates 9 specific endpoints (groundwater, streamflow, etc.) with brief explanations, distinguishing it from sibling pulse tools that cover other data domains.

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 implies usage for water-related queries via its endpoints, but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it or prerequisite conditions.

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