rdw_open_data_search

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

The description adds useful behavioral context beyond the readOnlyHint and openWorldHint annotations by detailing search modes and providing example query formats. However, it does not disclose potential rate limits, error states, or restrictions.

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 at two sentences, with no redundancy. It front-loads the main purpose and immediately provides practical examples.

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?

The description covers the basic search functionality but omits the return format and does not explain the 'rows' parameter's role in pagination. Given the tool's simplicity and presence of annotations, it is adequate but has gaps.

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?

With schema description coverage at 50%, the description adds value for the 'query' parameter by listing example formats and clarifying license plate lookups. However, the 'rows' parameter receives no explanatory text, leaving its purpose ambiguous.

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 RDW open vehicle data (Dutch vehicle registry) and specifies two search modes: by license plate or keywords. This provides a specific verb-resource pair and distinguishes it from sibling tools focused on other Dutch 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?

The description implies usage for Dutch vehicle data queries but gives no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or provide criteria for selecting among siblings.

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