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, OIG LEIE exclusion). However, it says nothing about permissions, cost/rate limits, fuzzy-match behavior on non-exact NPIs, or whether a missing record is an error versus an empty result — meaningful gaps for a compliance lookup.

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?

One sentence, front-loaded with the alias relationship, with no filler. The colon-separated structure is slightly dense but readable; nothing is wasted.

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?

No output schema and no annotations mean the description must define the return shape and safety profile, and it only partially does — it lists the domains checked but not the fields returned or failure modes. The NPI parameter is also left entirely undefined. Adequate but with clear gaps for a compliance-critical lookup.

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 single required parameter 'npi' has 0% schema description coverage, and the description does not compensate at all — it never specifies the expected 10-digit format, whether hyphens are accepted, or whether a name can be substituted. This is exactly the case where the description needed to fill the schema gap and does not.

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 uses a specific verb+resource ('Verify healthcare provider NPI registry record') and names the exact data domains covered (taxonomy specialty, practice location, LEIE exclusion status). It also explicitly identifies itself as an alias for verify_provider_npi, which is the key differentiator from that sibling — though it never explains why an agent should prefer one over the other.

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?

Calling it an 'Alias for verify_provider_npi' implies the two are interchangeable, but the description gives no guidance on which to pick, whether this one is deprecated, or whether behavior differs. Usage is inferable but not stated.

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