cdc_drug_overdose

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

Annotations declare readOnlyHint=true, and the description does not contradict this. The description adds useful context about the time range and demographic breakdowns, but it does not disclose deeper behavioral aspects such as data suppression rules, rate calculation methodology, or any limitations. This is acceptable given the annotations but not enhanced.

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 concise sentences, front-loaded with the main action and enriched by scope and use case. Every sentence earns its place with no filler or redundancy.

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 read-only query tool with four optional parameters and no output schema, the description conveys the dataset content, time range, and dimensions (state, sex, race, age). It omits explicit return format, but the schema's 'limit' description and the readOnly annotation provide enough context for an agent to expect a list of records. Minor gaps exist but are not critical.

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 baseline is 3. The description adds meaning beyond the schema by noting that the data includes death rates by race and age group, which are not filterable parameters in the schema. This gives the agent useful context about the dataset's content and dimensions.

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 drug poisoning/overdose mortality data by state for 1999–2016, using a specific verb and resource. It distinguishes itself from sibling CDC mortality tools by explicitly focusing on drug overdoses, making its purpose unambiguous.

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 a clear context for when to use the tool ('Critical for opioid crisis analysis') and conveys the data scope. It does not explicitly name alternatives or exclusions, but the use case is sufficiently implied for an agent to recognize when this tool is appropriate.

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