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

Annotations already indicate read-only safety. Description adds behavioral context about data semantics—state-reported program enrollment vs covered lives—which is a meaningful caveat beyond annotation. No contradiction.

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 sentences, front-loaded with purpose, second adds caveat. No wasted words.

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 output schema and rich annotations, description covers core purpose and important data caveat. A minor gap on date range behavior is understandable with output schema present.

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 only 33% (only state described). The description implies year parameters via 'annual' but does not explain to_year/from_year semantics such as range inclusivity or behavior when omitted. It does not compensate for the schema gap.

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?

Description uses specific verb 'Show', identifies resource as annual state Medicaid enrollment and managed care enrollment, and clarifies scope (any/comprehensive). It distinguishes from siblings like monthly and program mix tools. Not tautological.

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?

Second sentence provides an explicit exclusion: counts are program enrollment, not insurer-covered lives. This tells users when not to use the tool. However, it does not name alternative tools or explicitly state 'use this for X'. So it is clear but not fully explicit.

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