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

With no annotations, the description carries the full burden, and it does disclose the scope of checks performed (registry, taxonomy, location, LEIE exclusion). It says nothing about read-only nature being guaranteed, behavior on an invalid or unassigned NPI, partial-match handling, rate limits, or whether all four checks always run.

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?

A single dense sentence with the core action and the checked data sources front-loaded; nothing is wasted. The phrasing is slightly compressed ('Verify healthcare provider 10-digit NPI registry record') but remains parseable.

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 one-parameter read tool this covers the inputs and the scope of checks, but with no output schema in place the agent is left guessing what the response contains, such as whether it returns a pass/fail flag or the full NPPES record along with exclusion hits.

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 100% and there is a single required parameter already documented with an example, so the baseline of 3 applies. The description's only added detail, '10-digit', merely repeats the schema.

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 names a specific verb ('Verify') and resource ('healthcare provider 10-digit NPI registry record') and enumerates the data sources consulted (CMS NPPES, taxonomy, practice location, HHS OIG LEIE). However, it never distinguishes itself from the near-identical sibling lookup_npi_provider, nor from screen_sanctions_exclusions which also covers exclusions, so an agent comparing siblings has no basis for choosing.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named despite the sibling set containing both lookup_npi_provider and two sanctions-screening tools. Usage is only implied by the word 'Verify'.

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