cdc_nutrition_obesity

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

Annotations include readOnlyHint=true, and the description does not contradict this. The description adds useful context about the data source and available breakdowns (state, race, age, income, education), but does not disclose return format, pagination, or other behavioral details.

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?

Three short, front-loaded sentences with no filler. The first sentence states the purpose, the second lists exact topic values, and the third summarizes data dimensions. Efficient and well structured.

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 query tool with well-documented optional parameters, the description provides the source, topics, and stratifications. There is no output schema, but the data dimensions are clearly implied. A brief note on return shape would make it complete.

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 input schema already describes all three parameters with high coverage. The description adds little beyond listing topic values already present in the schema; the demographic context is informative but does not change parameter semantics.

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 uses a specific verb ('Get') and resource ('adult obesity, physical inactivity, and fruit/vegetable consumption by state from BRFSS'). It clearly differentiates this tool from sibling CDC tools by naming the specific health indicators and the BRFSS data source.

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 explicit when-to-use or alternative guidance is provided, but the description implies its use for BRFSS nutrition/obesity data by listing the topics and stratifications. It does not state exclusions or refer to sibling tools.

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