cdc_query

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

The readOnlyHint annotation already declares the safety profile. The description adds useful behavioral context by specifying the query syntax (SODA) and enumerating the exact dataset IDs, which helps the agent understand the scope. It does not disclose return format or pagination behavior, but provides meaningful context beyond the annotation.

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: one sentence stating the purpose and a second sentence listing datasets. The main verb and resource are front-loaded. The dataset list is informative and earns its place, providing key context without unnecessary verbosity.

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 has six parameters, a readOnly annotation, and no output schema. The description explains the purpose and lists datasets but omits output format details and does not reference the specialized sibling tools for when to use them. Given the moderate complexity, this is adequate but with clear gaps.

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 coverage is 100%, and each parameter has a descriptive example (e.g., "$where clause: \"year = '2021' AND state = 'New York'\""). The description only adds 'using SODA syntax,' which is redundant since the schema already mentions SODA $group, $order, etc. The description does not provide additional parameter-specific meaning.

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 the tool's purpose: 'Custom query against any CDC dataset using SODA syntax.' It explicitly lists the 12 available datasets, making the resource scope unambiguous. This distinguishes it from sibling tools like cdc_causes_of_death or cdc_covid, which are specific dataset wrappers.

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 by stating it's a custom query tool for any CDC dataset, but does not explicitly say when to prefer this over the specialized CDC sibling tools. No when-not-to-use or alternative guidance is provided, leaving the decision ambiguous for an agent.

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