search_datasets

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

With no annotations, the description prominently discloses that matching is deterministic substring-only, which is the key behavioral trait. It does not explicitly state read-only semantics or result behavior, but the output schema covers return shape, so the remaining gap is limited.

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 a single front-loaded sentence with no filler. Every phrase contributes either the resource scope ('registry-backed dataset metadata'), the operation ('Search'), or the key constraint ('deterministic substring matching only').

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?

For a one-parameter search tool with a 100%-covered schema and an output schema, the description and schema leave little ambiguity about invoking it correctly. A brief note on which metadata fields are searched would make it fully complete, but it is not a significant gap.

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% and the schema already documents case-insensitive substring matching, empty-string listing, and examples. The description adds no additional parameter meaning beyond the word 'only', which conveys exclusivity rather than new 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 uses a specific verb ('Search') and a clear resource ('registry-backed dataset metadata'), and the qualifier 'deterministic substring matching only' narrows the behavior compared with query or metadata-retrieval siblings. It does not explicitly name sibling tools, so it is unambiguous but not maximally differentiated.

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 phrase 'deterministic substring matching only' implies this is for exact substring lookups, and the schema supplements with empty-string and example guidance. However, the description itself gives no explicit when-to-use guidance or contrast with dataset_metadata/query_dataset, leaving alternatives to the agent's inference.

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