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

Annotations already provide readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context: the result is cryptographically attested, verifiable at a URL, and costs $1.00 USDC per call. These are useful operational details beyond the annotations. No contradictions exist.

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 compact but includes marketing-like phrases such as 'post-quantum signed settlement receipt' which add jargon without clear functional value. The core purpose, usage, and cost are front-loaded, but the trust/verification sentences could be trimmed for clarity. It is appropriately sized but not every sentence earns its 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?

With no output schema and no description of the return value, an agent cannot infer what a screening result looks like (e.g., boolean, list of matches, status). The description mentions the attested payload and verification URL but does not explain how to interpret the response. For a simple but critical compliance tool, the absence of return-format guidance is a significant gap.

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 0%, so the description must compensate for parameter meaning. It explicitly references 'provider name or NPI', identifying both parameters (npi and provider_name), which is helpful. However, it does not clarify whether one is mandatory, what happens if both are supplied, or how the 'list version and as-of date' relate to the parameters. The extra phrase about the attested payload may confuse rather than clarify parameter semantics. Adequate but with clear gaps.

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 HHS OIG LEIE by provider name or NPI', naming the specific resource (HHS OIG LEIE) and the verb (screens). It also includes the intended use case (credentialing healthcare providers or verifying vendor eligibility), which distinguishes it from sibling screening tools like get_ofac_sanctions_screening and get_sam_exclusion_screening. The purpose is unambiguous and specific.

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 explicitly opens with 'Use when credentialing a healthcare provider or verifying vendor eligibility against federal exclusions', giving a direct when-to-use instruction. It does not mention alternatives or when-not-to-use, but the specificity of the source (HHS OIG vs OFAC/SAM) implicitly routes the agent. This is clear context with no exclusions, warranting a 4.

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