get_hydro_inflows

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

With no annotations provided, the description carries the burden. It discloses the data source, variables, countries, and the fact that no API key is needed, but lacks details on units, update frequency, or data latency. Calling it a 'proxy' is a useful caveat, but more behavioral context would be expected.

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 a single concise sentence that front-loads the main purpose and key details (source, variables, countries, no API key). Every word earns its place; there is no redundancy or fluff.

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 tool with only two well-documented parameters, the description is adequate. It tells the agent what the tool does and its scope. However, without an output schema or any note on return format, the agent must guess what the response looks like, which is a notable gap.

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 schema provides 100% coverage of both parameters with descriptions, so the baseline is 3. The description adds extra context about countries and variables, but does not add meaning beyond what the schema already explains, such as how the period values affect the output.

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 what the tool does: provides a hydro inflow proxy using specific ERA5-Land variables for a set of countries. It distinguishes itself from generic weather tools like get_era5_weather by focusing on a derived proxy and naming the exact geographical scope.

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?

Usage is implied by the phrase 'Hydro inflow proxy' and the listed countries, but there is no explicit guidance on when to choose this over alternatives, nor any exclusions. The 'No API key' note is helpful but not enough to fully direct an agent.

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