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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real behavioural context beyond them: anonymous rate limits (60/hour, 300/day per IP and session), no API key required, key fallback after quota, and licence warnings. It stops short of describing pagination or truncation behaviour when limit is applied.

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?

Purpose is front-loaded in the first sentence, followed by output-characteristics and access/limits information, which is well ordered. The 'TerraMCP is a Wrench AI service' line is pure filler that could be dropped, costing it a point.

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?

With no output schema, the description does the right work by characterising the return ('source data and provenance', preserved units/quality codes, SI normalisation). Access terms, limits and licensing are covered, so an agent has what it needs; only pagination/truncation semantics for limit are unaddressed.

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 both parameters (station_id, limit) are fully documented in the schema itself, establishing a baseline of 3. The description restates the station_id provenance idea already in the schema and adds nothing about how limit interacts with results, so no lift beyond baseline.

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 uses a specific verb+resource ('Get NRW telemetry measures and latest observations for a station_id') and names the required key, so the agent knows the shape of the call. It does not, however, differentiate itself from near-neighbours like nrw_readings or nrfa_get_timeseries, leaving some ambiguity about which sibling to pick.

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 only implied: it takes a station_id from a station discovery tool, so the agent can infer it is a per-station data fetch. There is no explicit when-to-use/when-not guidance and no routing to or away from the many sibling reading/series tools (nrw_readings, ea_hydro_series, nrfa_get_timeseries), which is the main gap.

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