health.mortality-stats

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

No annotations are provided, so the description carries the burden. It discloses the data sources, time ranges, and dataset options, but does not mention authentication, rate limits, destructive actions, or what happens with missing parameters. Some behavioral context is present but not exhaustive.

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 front-load the main purpose and then detail the two datasets. Every sentence is necessary and efficient.

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 6 parameters, no output schema, and no annotations, the description provides reasonable completeness by explaining the datasets and their scopes. It could mention return format or pagination, but for a data retrieval tool, it is mostly sufficient.

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 low (33%), so the description partially compensates by explaining the 'dataset' parameter and clarifying the 'cause' parameter applies only to 'leading-causes'. However, it does not add meaning for 'year', 'limit', 'offset', or 'state' beyond what the schema already provides.

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 provides US mortality statistics from CDC NCHS, and distinguishes between two datasets ('leading-causes' and 'weekly-counts') with explicit time ranges and data types. It uses specific verbs and resources.

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 by explaining the two datasets but does not explicitly state when to use this tool over alternatives or when to choose one dataset over the other. No exclusions or context about when not to use it.

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