search_datasets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions returning a list of datasets with metadata, omitting details such as whether the operation is read-only, any rate limits, pagination behavior, or side effects. This is insufficient for a complex search tool.

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 three sentences and front-loads the primary purpose. While efficient, it could be more structured (e.g., bullet points for parameters) but remains easily readable.

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 7 optional parameters, no required params, and no output schema, the description gives a high-level overview but lacks guidance on default behavior when no query is provided, how filters combine, or how to handle large result sets. It does not reference sibling tools to aid selection.

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 input schema has 100% description coverage, so each parameter is documented. The tool description adds little beyond summarizing that search is by 'keywords, themes, spatial divisions, and other criteria,' which maps directly to the schema. It does not provide additional examples or deeper semantics.

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's purpose: searching for statistical datasets in the BFS catalog with various filters. It specifies the resource (datasets), action (search), and result (list with BFS numbers and metadata), effectively distinguishing it from siblings like get_dataset_info or list_themes.

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 explanation implies usage for searching by keywords, themes, etc., but does not explicitly state when to use this tool versus alternatives like get_dataset_info (for specific dataset details) or list_themes (for theme selection). No exclusions or when-not-to-use guidance is provided.

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