search_datasets

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

Despite no annotations, the description explains fuzzy-search behavior, match targets, case-insensitivity, and returned fields (id, name, description, etc.). It also notes the curated nature and version.

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 well-organized with a summary, code examples, and a return section. Every sentence adds value without being verbose.

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 (2 params, no nesting, output schema hinted), the description fully covers what an agent needs: search mechanism, inputs, and output format.

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 already covers 100% of parameters with descriptions and examples, so baseline is 3. The description adds context on search behavior and ranking, justifying a 4.

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 it performs a fuzzy-search on a curated dataset catalog, with examples and return types. It distinguishes itself from siblings like list_curated and describe_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?

Examples show when to use (searching by free-text) and implicitly contrast with sibling tools like list_curated for listing all datasets. No explicit when-not-to-use, but the context is clear.

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