cdc_drug_overdose

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

The description says 'Get', which aligns with the readOnlyHint annotation. No additional behavioral details (e.g., data source, update frequency, restrictions) beyond what annotations already provide. No contradictions.

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 concise sentences that effectively convey the tool's purpose and key information. No unnecessary words or repetition.

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 mentions 'death rates' but does not clarify the output structure (e.g., whether it returns counts, rates by population, or raw numbers). No output schema is provided, so more detail on return format would improve completeness. Adequate for a simple query tool.

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 each parameter having a description. The description adds little extra meaning, only listing the dimensions ('state, sex, race, and age group') which are already covered by schema parameters. Baseline score of 3 is appropriate.

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 explicitly states 'Get drug poisoning/overdose mortality by state' and details dimensions (state, sex, race, age group), clearly differentiating it from other CDC tools. It also provides context ('Critical for opioid crisis analysis').

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?

No guidance on when to use this tool versus alternatives, such as other CDC mortality tools (e.g., cdc_causes_of_death, cdc_mortality_rates). The description mentions opioid crisis but does not exclude use cases or provide selection criteria.

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