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

The description adds a crucial behavioral warning: 'Program counts overlap and must not be summed.' This is not conveyed by the annotations (readOnlyHint, idempotentHint, etc.) and is essential for correct interpretation of the data. This goes beyond what annotations provide.

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 a single well-structured sentence that leads with the action and resource, lists the relevant categories, and ends with a critical caveat. Every part earns its place without redundancy.

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 the presence of an output schema, complete parameter documentation, and strong annotations, the description only needed to add the overlapping-count warning, which it does. This makes the tool fully usable without further context.

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 provides full descriptions for both parameters (state and year), with 100% coverage. The description does not add additional parameter-level semantics beyond the schema; it focuses on the output categories. Thus the 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 uses a specific verb ('Show') and resource ('state Medicaid enrollment by managed-care program type'), and enumerates the program types (comprehensive MCO, PCCM, MLTSS, behavioral health, dental, transportation, PACE), which clearly distinguishes this tool from siblings like medicaid_managed_care_summary or medicaid_monthly_managed_care.

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 clearly implies when to use this tool: when the user wants enrollment broken down by managed-care program type. It does not explicitly name alternatives or exclusions, but the scope is clear enough for an agent to select it appropriately.

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