cdc_query

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat that. It adds the list of dataset IDs and their context (e.g., death 1999–2017), which is useful. However, it does not disclose behavior like return format, pagination, or that this is an ad-hoc query tool meant for cases where dedicated tools don't fit.

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 concise: one opening sentence and a list of datasets. The purpose is front-loaded, and the dataset list is dense but necessary. It avoids unnecessary fluff.

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 description tells the agent which datasets are available and that SODA syntax is used, which is sufficient for a generic query tool. However, it omits guidance about the existence of dedicated tools for the same datasets and does not explain when custom queries are needed. Given the lack of an output schema and the availability of dedicated siblings, this is a moderate 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%, so all parameters are already documented in the schema with examples. The description adds no parameter-specific meaning beyond what the schema provides, so it meets the baseline for full schema coverage.

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: a custom query against any CDC dataset using SODA syntax. It lists specific dataset IDs, which makes the resource concrete. It distinguishes itself from dedicated CDC tools (like cdc_life_expectancy) by being generic, though it does not explicitly name those siblings.

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 provides no guidance on when to use this tool versus the dedicated CDC dataset tools (e.g., cdc_life_expectancy, cdc_mortality_rates). It does not mention alternatives or exclusions. An agent might incorrectly choose this generic tool when a specialized tool would be more appropriate.

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