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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: a 1-20 batch cap, pre-flight check-digit validation, and separate reporting of invalid versus unknown NPIs, which tells the agent partial failures are possible and distinguishable.

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?

Two front-loaded sentences covering what is fetched, from where, how many, and how errors are handled. No filler; every clause carries information.

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 with annotations covering read-only and open-world access, this is nearly complete — it even lists the return fields in lieu of an output schema and explains error reporting. Only the NPI string format and per-item versus whole-batch failure semantics are left unstated.

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?

With a single parameter at 0% schema description coverage, the description compensates: it establishes that 'npis' is a batch of NPI numbers and that the 1-20 cardinality is enforced, mirroring the schema's minItems/maxItems. It stops short of stating the NPI digit format or whether the array is all-or-nothing.

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 (Fetch), resource (providers), keying (by NPI number), source (live CMS NPI Registry) and enumerates returned fields. This implicitly separates it from search_providers and count_by_specialty, but no sibling is named, so the differentiation is inferred rather than stated.

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 'by NPI number' framing implies this is the direct-lookup path versus search_providers, and the mention of check-digit validation hints at a relationship with validate_npi. However, there is no explicit when-to-use/when-not statement or named alternative.

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