wetten_bwb_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's value is in adding context about the index used (overheidbwb.titel) and the return fields. 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 concise, front-loading purpose, and every sentence adds value. No extraneous words.

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?

Describes the index used and return fields, which is helpful given no output schema. However, it omits pagination behavior and parameter relationships (e.g., top/limit/offset).

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?

Only the query parameter is described in the schema and reinforced in the description. The other six parameters (top, limit, offset, dryRun, verbose, outputFormat) lack explanation in both schema and description, leaving the agent underinformed.

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?

Description clearly states the tool searches Dutch consolidated legislation via KOOP SRU, matching keywords against a title index, and returns specific fields. This distinguishes it from sibling tools like officiele_bekendmakingen_search or rechtspraak_search_ecli.

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?

Explicitly advises 'Pass title keywords only, not full sentences,' providing clear usage guidance. However, it does not explicitly state when to use this tool over alternatives, though the specificity implies its niche.

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