search_datasets

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

No annotations provided, so the description carries full burden. It discloses that the tool returns dataset codes and recommends Czech terms for best results. It does not mention rate limits or authorization, but as a search tool it is inherently read-only and non-destructive, so the transparency is adequate.

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 two short paragraphs. The first sentence is clear and front-loaded. The list of terms is easy to scan. Could be slightly more concise, but overall it earns its place without unnecessary 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?

Given the tool's simplicity (one string parameter) and the presence of an output schema, the description is complete. It explains what the tool does, how to use it (keyword search, Czech terms), and what to do with the results (use with get_dataset/get_dataset_selections). No 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?

The single parameter 'query' is described as a keyword search. The description adds meaning beyond the schema by stating it works best with Czech terms and providing common examples. Schema coverage is 0% but the description compensates well for a simple string parameter.

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 states 'Search for statistical datasets by keyword' which clearly specifies the action (search), resource (statistical datasets), and method (by keyword). This distinguishes it from siblings like list_datasets (lists all) and get_dataset (retrieves specific).

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 provides useful context: 'Search works best with Czech terms' and includes a list of common Czech terms with English translations. It also explains that results are 'dataset codes usable with get_dataset() and get_dataset_selections().' However, it does not explicitly state when to use this tool versus alternatives like search_selections, which would make it a 5.

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