env_water_quality

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

With no annotations, the description must fully disclose behavioral traits. It only says 'reference data,' implying a read operation, but does not explicitly state read-only, data freshness, or whether multiple indicators are returned. No details on permissions or side effects are provided.

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 sentence of 12 words, efficiently conveying the core purpose without unnecessary detail. It is front-loaded and every word earns its place.

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 no output schema, the description hints at return fields ('chlorophyll, turbidity') but lacks units, temporal scope, or response structure. For a simple two-parameter tool, it is adequate but could be more informative.

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% with basic descriptions ('Latitude', 'Longitude'). The tool description adds 'for a coordinate' but does not enhance parameter meaning (e.g., coordinate system or precision). Baseline 3 is appropriate as the description repeats the schema's intent without adding value.

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 identifies the tool as providing water quality indicators (chlorophyll, turbidity) for a coordinate. It uses a specific verb ('reference data') and resource ('water quality indicators'), and it distinguishes from siblings like env_air_pollution or env_ocean_temp by focusing on water quality parameters.

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?

No usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention any preconditions or exclusions. Among siblings, there is a potentially overlapping tool like ocean_chlorophyll, but no differentiation is given.

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