Search CDC Health Datasets

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

The annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds useful context about return fields (dataset ID, name, description, category) but does not disclose further behavioral traits like pagination or rate limits, which would elevate it to a 5.

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 extremely concise: two sentences that convey the tool's purpose, scope, examples, return fields, and sibling guidance. Every sentence is essential and front-loaded with the most important information.

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 has 3 optional parameters, no output schema, and comprehensive annotations, the description provides all necessary context: what it does, when to use it, what it returns, and how it relates to cdc.health.query. It is fully complete for agent decision-making.

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% description coverage, so the schema already documents all parameters. The description adds value by giving example search keywords ('covid deaths', 'vaccination rates') and specifying the result limit range (1-50, default 20) which is also in the schema but reinforced here. This slightly exceeds the baseline of 3.

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 searches over 1,400 CDC datasets, lists example topics (COVID-19, chronic disease, vaccination, etc.), and specifies the return fields (ID, name, description, category). It also distinguishes itself from the sibling tool cdc.health.query by directing users to use dataset IDs with that tool to fetch data.

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 explicitly tells when to use this tool (to search datasets) and directs users to the sibling tool cdc.health.query for fetching data. This clear alternative guidance helps the agent choose correctly.

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