health.mortality-stats

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the data is read-only, any rate limits, authentication requirements, or update frequency. The description only states the data source and dataset contents.

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 extremely concise with two sentences, each carrying essential information. No unnecessary words. It front-loads the source and then explains the two datasets.

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?

Given no output schema and low schema coverage (33%), the description should provide more context about output format, valid cause values, and time range per dataset. It covers basics but leaves gaps for effective tool usage.

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?

The description clearly explains the two dataset options and their data offerings (e.g., age-adjusted rate by state and top-10 cause for leading-causes), which adds meaning beyond the schema's enum. However, it does not describe limit, offset, or year behavior beyond schema. Schema coverage is 33%, and the description partially compensates.

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 it provides US mortality statistics from CDC NCHS and details two datasets with specific content and time ranges, distinguishing it from sibling health tools that focus on hospitals, providers, etc.

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 does not explicitly state when to use this tool versus other mortality data tools or provide guidance on selecting between the two datasets beyond the implicit time range and granularity. No alternatives are mentioned.

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