rijksoverheid_search

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

Beyond annotations (readOnlyHint, openWorldHint), description reveals key constraints: server-side keyword search, ~20 results per query, no pagination. Adds value.

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?

Three sentences covering tool identity, behavioral constraint, and usage. Efficient but could be slightly more structured (e.g., bullet points for parameters).

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?

Despite clear purpose, the description omits details for most parameters (date filters, limits, offsets) and lacks output schema information. For a search tool with 10 parameters, this is incomplete.

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 covers 'query' and 'type' parameters. The remaining 8 parameters (top, limit, offset, date_from, date_to, dryRun, verbose, outputFormat) are not described in the tool description, and schema descriptions are minimal or missing. Schema coverage is only 20%, so description fails to compensate.

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 it searches Rijksoverheid.nl content via RSS search platform, distinguishing it from sibling tools that target other government databases.

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 explicit guidance on using topic keywords and the 'type' parameter ('news' vs 'all'). Does not explicitly contrast with alternatives but sufficiently instructs on usage.

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