cdc_covid

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

Annotations already provide readOnlyHint=true, and the description aligns with 'Get'. It adds useful context like data recency and state abbreviation format, but does not disclose behavior for missing parameters, default limit, or pagination. The description complements annotations but leaves gaps.

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?

Two sentences, front-loaded with the core purpose and key details (state codes, date range). No extraneous 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?

No output schema exists, and the description does not describe the return format (e.g., fields, data structure). It also fails to differentiate from the similar sibling cdc_weekly_deaths or clarify behavior when no state is provided. This leaves agents guessing about the response.

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% with descriptions for both state and limit. The description partially reinforces the state parameter but offers no new insight beyond the schema. With full schema coverage, baseline is 3; no added value.

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 verb 'Get', the resource 'COVID-19 weekly case and death counts', and the scope 'by state'. It also notes the data timeframe (through early 2023) and provides state format examples, effectively distinguishing it from sibling tools like cdc_weekly_deaths.

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 implicitly suggests use for COVID-19 case/death data but does not explicitly state when to use this tool versus alternatives like cdc_weekly_deaths or other CDC tools. No exclusionary language or direct comparison is provided.

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