cbs_search_datasets

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds that results are returned as a CSV string, which is useful but not a major behavioral disclosure beyond annotations.

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: two sentences for overall purpose, followed by a structured bullet list for parameters. It avoids fluff and is easy to scan.

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?

Given the tool's simplicity and the existence of annotations and output schema mention (CSV string), the description fully covers what the tool does, its parameters, and its return type. No gaps remain for this search tool.

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 100%, with each parameter already documented in the schema. The description repeats those descriptions verbatim (e.g., 'query (str): Search term'). It adds no new meaning or context beyond what the schema provides.

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 'Searches for datasets in the CBS OData Catalog by keyword,' specifying the action (searches), resource (datasets), and context (CBS OData Catalog). This distinguishes it from sibling tools like cbs_list_datasets (which lists all) and cbs_inspect_dataset_details (which shows details of a specific dataset).

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 when a keyword search is needed, but it does not explicitly state when to use this tool over alternatives (e.g., cbs_list_datasets). Given multiple siblings, explicit when-to-use and when-not-to-use guidance would be helpful.

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