dso_omgevingsdocumenten_search

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

Annotations (readOnlyHint, openWorldHint) are consistent. Description adds critical context: 'Discovery-only search', 'Returns metadata only (id, titel, type, bevoegd gezag, geldigheidsdatums, viewer-link), geen juridische tekst'. This goes beyond the annotations to specify exactly what the tool does not return.

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?

Two concise sentences: first identifies the tool and its scope, second clarifies output and requirement. No redundant information, every sentence is substantive.

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 search tool with 5 parameters (none required) and no output schema, the description covers domain, output fields, and a constraint (API key). It lacks details on pagination or sorting, but the schema's 'rows' parameter hints at pagination. Overall adequate for an agent to understand the tool's purpose and output.

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 80% (high), so baseline is 3. The description does not elaborate on the parameters; the schema already provides descriptions for query, bevoegdGezag, documentType, typeBevoegdGezag. The description adds no extra parameter guidance beyond mentioning the API key requirement.

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?

Clearly states it's a 'Discovery-only search for DSO Omgevingsdocumenten' and lists specific document types (omgevingsplannen, etc.). The verb 'search' and resource 'DSO Omgevingsdocumenten' are distinct from sibling tools which are various other Dutch government data sources.

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?

Mentions prerequisite (DSO_API_KEY) and implicitly indicates this tool is for retrieving metadata of Omgevingsdocumenten under the Omgevingswet. Does not explicitly exclude alternatives, but sibling tools are so different in domain that there's little ambiguity.

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