rijkswaterstaat_waterdata_search

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

Annotations (readOnlyHint, openWorldHint) already convey safe, open-ended behavior. The description adds minimal behavioral context beyond 'search catalog,' which is baseline. No contradictions.

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, front-loaded sentence with no wasted words. However, it omits potentially useful details (e.g., result type) that could be added without bloat.

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 simple search tool with 2 parameters and no output schema, the description is minimally adequate. It covers the tool's domain but lacks specifics on result format or pagination. Sibling names provide some context.

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 50% (only query described). The tool description repeats the keyword advice but adds no new meaning. The 'rows' parameter lacks description in both schema and tool description, leaving its purpose unclear.

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 searches a water data catalog with specific topics (water levels, waves, flow, quality). The sibling tool 'rijkswaterstaat_waterdata_measurements' hints at a separate retrieval function, but the description does not explicitly distinguish itself, preventing a 5.

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 advises 'Use water management topic keywords,' and the query parameter schema warns against full questions. However, no guidance is given on when to use this search versus the measurements sibling or other alternatives.

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