cbs_iv3_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the tool is clearly safe and open-ended. The description adds the OData source and dimension exploration mode, but does not explain pagination, rate limits, or the effect of the 'dryRun' parameter. Behavioral transparency is adequate but not enhanced significantly.

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 three sentences, each adding value: purpose+source, filterable fields, dimension exploration. No wasted words, front-loaded.

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 tool has 13 parameters, none required, with options for pagination, dry run, and output format. The description only covers the search filter aspect and dimension exploration, missing explanations for pagination, dryRun, verbose, and outputFormat behavior. Given the complexity, the description 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?

Schema description coverage is 54%, leaving several parameters (top, limit, offset, dryRun, verbose) undocumented in the schema. The tool description mentions filtering fields but does not explain these numeric/boolean parameters. However, it does add context about OData source and dimension exploration. Parameter semantics are partially improved but not fully compensated.

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 explicitly states the tool searches CBS Iv3 municipal/provincial finance statistics, listing four filter dimensions and an explore mode for dimension values. This distinguishes it from sibling CBS tools like cbs_observations (general observations) and cbs_tables_search (table metadata).

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 retrieving CBS finance statistics with filtering, but does not specify when to use alternatives like cbs_observations or cbs_tables_search. It lacks explicit when-not or alternative guidance.

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