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

Annotations already declare readOnly, idempotent, non-destructive behavior in a closed-world dataset, so the safety profile is covered. The description earns credit by disclosing the actual content envelope: per-level-of-care counts, Medicaid/Medicare/sliding-scale/no-charge breakdowns, and accompanying list-page URLs. It omits data freshness and whether counts are deduplicated, which keeps it from a 5.

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?

A single front-loaded sentence that opens with the scope (one state/territory) before enumerating contents, with no filler. The nested clause structure and parenthetical lists make it dense to parse, but every clause carries information.

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?

No output schema exists, so the description must describe the return value, and it does so in detail: grouped counts, insurance/fee acceptance tallies, and page URLs. Missing only ancillary context such as data source recency or whether the counts are mutually exclusive by level of care.

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 100%, with the two-letter pattern and an example already documented in the schema. The description only adds that territories are included ('one US state or territory'), which is marginal over the schema's own 'state or territory code' wording. Baseline 3 applies.

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 names a specific resource (SAMHSA-listed treatment programs) and a specific output shape (counts per level of care, insurance acceptance counts, and list-page URLs) scoped to one state. That is clearly an aggregate overview rather than a single-record lookup, so an agent can infer the split from find_programs/get_program. It stops short of naming those siblings explicitly.

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?

Usage is only implied: the phrase 'how many ... at each level of care' signals a state-level aggregate, which contrasts with per-program lookups. There is no explicit statement of when to prefer this over find_programs or get_program, and no exclusions or prerequisites are given.

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