search_datasets

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: fuzzy search, case-insensitivity, ranking by relevance, and curated dataset scope. However, it does not mention side effects, authentication needs, or data freshness. For a read-only search tool, this is acceptable but not exemplary.

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: one paragraph explaining the tool, followed by two clear examples and the return type. Every sentence adds value, and the structure is well-organized with no redundancy. It is appropriately sized and 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?

Given the tool's low complexity, presence of an output schema (implied), and sibling tools, the description is largely complete. It covers the search scope, examples, and return format. It could optionally mention that results are limited to curated datasets, but it already states 'curated WGEA dataset catalog'.

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% coverage with descriptions and examples for both parameters (query and limit). The description does not add extra parameter information beyond what the schema provides, so a baseline score of 3 is appropriate per rules.

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 'Fuzzy-search the curated WGEA dataset catalog', specifying the verb (fuzzy-search) and the resource (curated WGEA dataset catalog). It distinguishes from sibling tool 'list_curated' by emphasizing searchability and mentions the seven specific datasets, making the purpose unambiguous.

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 finding datasets by text query, and examples demonstrate common searches. However, it lacks explicit guidance on when to use this tool versus alternatives like 'list_curated' (which lists all datasets). No when-not-to-use or exclusion criteria are provided, so it is merely adequate.

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