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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the description is free to add real value: it names the authoritative source (CMS NPPES), notes it is free, and enumerates the status outcomes (active / deactivated / not_found) plus returned fields. It omits rate-limit, caching, or freshness caveats, keeping it short of a 5.

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?

Front-loaded with the core statement, then usage triggers, then return payload - a sensible order. The trigger-phrase list is long and quasi-keyword-stuffed, but each phrase is plausibly useful for retrieval, so the verbosity mostly 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, the description carries the burden of describing returns and does so concretely: status enum values, name, taxonomies with license numbers, addresses, enumeration and update dates. Combined with the single required parameter, an agent has everything needed to call it and interpret results.

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?

Only one parameter and the schema already documents it fully via pattern '^\d{10}$' and a description, so coverage is 100%. The description adds nothing about format or edge cases (leading zeros, spacing) beyond 'by number', so baseline 3 applies.

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: validates an NPI number against the CMS NPPES registry. It is clear on its own, but it never distinguishes itself from close siblings like check_npi_status and lookup_npi, which sound like they do the same thing.

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 concrete user phrasings that should route here ('verify this NPI', 'is my NPI active', 'did my NPI get deactivated', 'what taxonomy is on my NPI'), which is strong positive guidance. It lacks any when-not condition or explicit routing between this tool and check_npi_status / lookup_npi, which is the main ambiguity.

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