ngr_discovery_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which cover safety and external sources. The description adds that it searches for geospatial metadata, which is consistent. It does not contradict annotations, but does not provide additional behavioral details like pagination or error handling.

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 one sentence and very concise. It communicates the key purpose without extraneous words. However, it could be slightly more informative without losing brevity.

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 two parameters and no output schema, the description covers the source and type of data. It is adequate but does not explain return value format or what to expect from results, leaving some ambiguity.

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 50%: only the query parameter has a description. The tool description does not add any information about the rows parameter (e.g., that it limits results). The query parameter examples are helpful but already in the schema.

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 Nationaal GeoRegister for geospatial metadata, including maps and WMS/WFS services. It specifies the resource (NGR) and the type of content, distinguishing it from sibling tools that search other Dutch government data.

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 says to use spatial data topic keywords, which gives a usage hint. However, it does not explicitly state when to use this tool versus alternatives like bag_address_detail or cbs_tables_search. The context is implied but not formally guided.

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