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

The description goes well beyond the annotations by detailing exactly what is returned (DOB, state, city, specialty, NPI, exclusion start, statutory reason, match_confidence), and by warning that it never returns a bare yes/no because multiple excluded people can share a name. This gives the agent important behavioral context that annotations alone do not 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 dense but organized and front-loaded with the core screening purpose. Every sentence adds relevant detail, resulting in a comprehensive yet efficient explanation. It could be slightly tighter, but it earns its length given the tool's nuanced output behavior.

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?

With no output schema, the description fully explains the return value composition, including distinguishing fields and match_confidence. It also covers source, use cases, parameters, and the crucial caveat about shared names and identification. An agent has enough information to call the tool correctly without needing additional structured data.

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 baseline is 3, but the description adds real meaning: it clarifies that npi turns a name lead into an identification, explains that state narrows candidates for common names, and notes the name field accepts any order. This is useful enrichment beyond the schema's field-level descriptions.

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 clearly states the tool screens a person or business name or NPI against the HHS OIG List of Excluded Individuals/Entities, and gives concrete example questions. It is specific and unambiguous, but it does not explicitly differentiate itself from the sibling tool provider_exclusion_coverage, so it misses the 'distinguishes from siblings' bar for a 5.

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 gives clear use cases such as pre-payment or credentialing screening and answers like 'is Dr X excluded'. It also explains when to pass an NPI. However, it never mentions when not to use this tool or names an alternative, so it falls short of explicit when-not guidance.

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