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

Annotations already declare readOnly, idempotent, and non-destructive hints, so the safety profile is covered. The description adds valuable behavioral context: that a match is a screening lead, not final identity confirmation, and advises verification with HHS OIG. It also mentions source freshness and evidence IDs, which enriches the agent's understanding of the output. No contradiction with annotations.

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 concise, front-loaded with the core action, and every sentence adds value: the action, the return content, and a critical caveat. There is no redundancy or 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?

For a single-parameter, read-only lookup with annotations covering safety and idempotency, the description fully covers what the tool does, what it returns, and the important limitation of a match. No missing information that would prevent an agent from calling it 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?

The schema description for the sole parameter 'npi' has 100% coverage, so the schema already fully documents the format (exactly 10 digits) and the placeholder rejection. The description only repeats the '10-digit' requirement without adding new semantic detail, so the baseline of 3 is appropriate.

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 action ('Check a 10-digit NPI'), a precise resource ('self-hosted HHS OIG List of Excluded Individuals/Entities (LEIE)'), and the return value (matching exclusion records). It clearly distinguishes itself from sibling tools like leie_search_exclusions (which searches by other criteria) by focusing on NPI-based lookup, even though it doesn't name them 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?

The description clearly implies the usage condition: when you have a 10-digit NPI, use this tool. It does not explicitly mention alternatives or when-not-to-use, but the context is unambiguous. Since there is no exclusion guidance, it earns a 4 rather than a 5.

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