overheid_api_register_search

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

Adds that an API key is required, which is not covered by annotations. The readOnlyHint is consistent with 'search' behavior. 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?

Two concise, front-loaded sentences with no wasted words. Essential information is prioritized.

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?

Given the absence of output schema, the description does not specify return values. However, the tool's purpose is clear and the parameter details are mostly self-explanatory. Slightly incomplete but adequate.

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 description adds useful context for the 'query' parameter (examples, prohibition of full questions) but does not explain other parameters like top, limit, offset, dryRun, verbose, or outputFormat. Schema coverage is low (14%), so the description partially compensates.

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 the Dutch government API register using API/data topic keywords, distinguishing it from sibling tools like data_overheid_datasets_search which search datasets.

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?

Provides examples of valid queries and warns against passing full questions, but does not explicitly state when not to use this tool or suggest alternative tools.

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