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

Annotations cover only readOnly/openWorld/idempotent hints, so the description carries the rest: per-call price ($0.01), payment mechanism (x402 USDC on Base via _meta, MPP on the HTTP URL), and the non-obvious billing behavior that an empty candidate set is still a paid 200. It also discloses the outputs and the limits of the result's authority.

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?

Very compressed and every clause carries information, but it opens with pricing rather than the purpose, so the core 'what it does' arrives in sentence two. Structure is dense yet mostly earn-your-place.

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?

An output schema exists, so return fields need not be explained, yet the description still names the match payload (name score, reasons, NPI, state, specialty, exclusion type, date). Combined with billing, payment, and confirmation caveats, nothing an agent needs to invoke this correctly is missing.

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 description coverage is 83%, so the schema already documents npi, name, lists, state and min_score. The description adds only that NPI is acceptable input and that state merely re-ranks; limit and min_score are not elaborated, so this sits at the baseline for high-coverage schemas.

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?

States a specific verb and resource: screen a person/business name or NPI against the HHS-OIG exclusion list (LEIE, Medicare and Medicaid). The named dataset and the 'potential matches only' scope make it immediately distinguishable from sibling tools such as sanctions_screen.

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?

Gives explicit when-not conditions ('Not for employment or credit decisions', 'Not a determination: confirm a match on the OIG online search with the SSN or EIN') and routes agents to a free companion endpoint for list dates and code meanings. It stops short of naming sibling screening tools (e.g. sanctions_screen) as alternatives for other datasets.

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