cdc_covid

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

Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent already knows this is a safe, non-mutating operation. The description adds a temporal constraint (data through early 2023) and clarifies the state format, which supplements the annotations with useful behavioral context without contradicting them.

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 short sentences, front-loading the core purpose and then providing a key usage detail (state abbreviations). No filler or redundant information; every sentence serves a purpose. It is efficient and to the point.

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?

For a simple read-only tool with clear schema coverage and no output schema, the description covers the main dataset, time frame, and parameter format. It does not mention pagination or optional output details, but given the simplicity and annotations, the description is sufficient for correct invocation. Missing details like default behavior of limit are minor.

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%, so both parameters (state and limit) are already described in the schema. The description reinforces the state format but does not add new meaning beyond the schema. The limit parameter is fully self-explanatory in the schema. High schema coverage means the description need not duplicate explanations, baseline 3 is warranted.

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 retrieves COVID-19 weekly case and death counts by state, with a specific time frame (data through early 2023). It uses a specific verb ('Get') and resource ('COVID-19 weekly case and death counts'), and is distinct from siblings like cdc_causes_of_death or cdc_weekly_deaths by specifying the data type and granularity.

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 for COVID-19 data retrieval but does not explicitly state when to use it versus other CDC tools (e.g., cdc_weekly_deaths or cdc_causes_of_death). It provides no conditions for selection or alternatives, leaving the agent to infer based on the data focus.

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