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

Beyond the read-only and idempotent annotations, the description discloses important behavioral traits: this is a current-snapshot list rather than an ever-excluded file, reinstated providers are removed, and every match is therefore currently excluded. It also explains that NPI matches are identifications while name matches are only candidate leads because the list lacks date of birth.

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 front-loaded with the core question and screening action, followed by relevant caveats. It is somewhat long, especially the sibling enumeration, but most sentences add substantive screening guidance rather than filler.

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?

Although there is no output schema, the description provides the source, scope, keyless access, match interpretation, and the current-snapshot limitation. An agent has enough context to decide when and how to call this tool correctly.

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%, so the parameter descriptions already carry most semantics. The tool description still adds useful interpretation by emphasizing that passing npi converts a name lead into an identification and by explaining why name matches remain candidates even when exact.

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 states a specific screening action against a specific resource: checking a provider or business against the Georgia DCH OIG excluded individuals and entities list. It explicitly differentiates this tool from the federal LEIE and names the New York, California, Texas, Florida, and Pennsylvania counterparts.

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?

It gives clear when-to-use examples, including pre-payment and credentialing screening for Georgia Medicaid providers, and explains how to escalate a name lead to an identification by passing an NPI. It also names adjacent alternatives such as the LEIE pack and state sibling tools.

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