rijkswaterstaat_waterdata_measurements

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

Annotations already mark the tool as read-only (readOnlyHint=true) and openWorldHint=true, so the description adds value by specifying it returns actual measured values with timestamps, indicating real-time freshness. No contradiction with annotations.

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 two sentences, front-loaded with key information, and no unnecessary words. Every sentence adds value.

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 only vaguely states 'Returns actual measured values with timestamps.' It does not describe the return structure (e.g., station, unit, fields), which is insufficient for an agent to parse the response correctly.

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 query parameter has a detailed description with examples, but the rows parameter (integer with defaults) is not mentioned in the description. Schema coverage is 50%, so the description partially compensates but leaves rows unexplained.

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 tool retrieves real-time water measurements (water levels, waves, flow, temperature) from Rijkswaterstaat stations, specifying the verb 'Get' and the resource. It differentiates from sibling tools like 'rijkswaterstaat_waterdata_search' by emphasizing real-time measured values with timestamps, but does not explicitly contrast them.

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 retrieving latest real-time measurements but does not explicitly state when to use this tool versus alternatives. No when-not or alternative tool guidance is provided.

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