odp_search_datasets

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

No annotations are provided, so the description carries the transparency burden. It implies a read-only search and indicates pagination through offset/limit, but it doesn't describe response contents, authorization needs, rate limits, or the exact scope of dataset results.

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 compact and front-loaded: clear purpose first, then an explicit usage condition, then the Args block. No filler or redundant restatement.

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?

The tool is a simple search with only three optional parameters, and an output schema is present so return values need not be spelled out in the description. The description adequately explains the tool's purpose, use cases, and parameter semantics; a little more context about dataset scope or exclusions could fill the remaining 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?

The schema itself has no descriptions, but the Args section compensates by defining each param: query is for dataset names/descriptions, offset is the starting position, and limit is the max result count. This is sufficient for an agent to understand and invoke parameters correctly.

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 clarifies the tool as searching USPTO bulk data products/datasets, giving a specific verb and target resource. This clearly differentiates it from the many sibling tools that search patents, applications, trademarks, or other records.

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 explicit 'USE THIS TOOL WHEN' line tells the agent it is for finding USPTO bulk download datasets for large-scale analysis. It doesn't name alternatives or when not to use it, but the resource is distinct from the sibling tools.

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