nhgis_search_datasets

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

With no annotations, the description carries the burden. It discloses a key behavioral trait: 'Fetches all available datasets and returns those whose name, group, or description match,' which hints at a broader fetch-then-filter approach. It does not cover pagination or return format, but for a simple read-only search, this is adequate.

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 two sentences long, front-loaded with the action, and every sentence adds value. The first sentence defines the operation and matching logic, the second provides usage guidance. No wasted words.

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 simple (1 parameter, no output schema), and the description fully explains what it does, what it matches on, and when to use it. It doesn't describe return values, but that is not required given the lack of a complex output schema and the simplicity of a search operation.

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 already covers the keyword parameter with a description identical to the tool's explanation: 'Search term to match against dataset name, group, and description (case-insensitive).' The tool description adds no new semantic details beyond what the schema provides, so baseline 3 applies.

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 'Search NHGIS datasets by keyword' with a specific verb and resource. It further specifies the matching criteria (name, group, description) and distinguishes itself from sibling tools like nhgis_search_data_tables by mentioning 'before drilling into specific data tables.'

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?

It provides explicit usage context: 'Use this to find which datasets cover a topic or census year before drilling into specific data tables.' This implies it is a discovery-first tool, though it does not explicitly name alternative tools or state when not to use it.

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