getapi_kvk_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it only gives a purpose and an endpoint hint. It says nothing about authentication requirements, rate limits, pagination, or what the search returns, leaving a significant gap for an unannotated tool.

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?

A single short sentence with the endpoint reference is efficiently front-loaded and wastes no words. It is arguably too terse, but there is no bloat or redundancy, which is what this dimension measures.

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 no annotations and no output schema, the description is incomplete: it never indicates how results are retrieved, what they contain, or how the empty parameter set is meant to function. An agent cannot confidently invoke a 'search' with no criteria from this text alone.

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 tool takes zero parameters, so the baseline is 4. The description correctly adds nothing to clarify, since there is no schema detail to compensate for. The notable oddity of a 'search' with no query parameters is not addressed, but no parameter semantics are required.

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?

States a clear verb and resource: 'Zoeken in KVK Handelsregister' (Search in the KVK Trade Register), reinforced by the 'search' name and the [GET /v1/kvk/search] endpoint hint. It does not explicitly distinguish itself from the sibling getapi_kvk_detail / getapi_kvk_detail_branch, though the verb does implicitly differentiate search from detail lookup.

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 offers no guidance on when to use this tool versus alternatives like getapi_kvk_detail or getapi_kvk_detail_branch. There is no mention of context, prerequisites, or exclusions beyond the bare purpose statement.

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