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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on domain behavior and adds real value: the data source (CMS NPPES) and, more importantly, a list of things the record does NOT establish (licensure, credentialing, network participation, practice status). It does not address not-found handling or record freshness, which keeps it from 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?

Two sentences, front-loaded with the operation and data source, and the second sentence uses its space to prevent a concrete misuse of the data. There is no redundant restatement of the title or schema.

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?

This is a low-complexity single-parameter lookup with a full input schema and an output schema, so return-value detail is unnecessary. The only meaningful omission is behavior on an unknown or invalid NPI, which would round out an otherwise complete definition.

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 coverage is 100%: the single parameter has a type, a strict 10-digit pattern, and a concrete example. The description only restates that the input is a 10-digit NPI, adding no format, normalization, or edge-case guidance beyond the schema, so the 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?

The description gives a specific verb and resource ("Look up a single U.S. healthcare provider or organization"), names the exact identifier type, and explicitly narrows scope to a single record retrieved by NPI. That single-record, identifier-based framing naturally separates it from the sibling tools search_providers and providers_near without needing to name them.

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 makes the usage context clear (you already have a 10-digit NPI and want one record), and the caveat sentence implicitly tells the agent not to treat the result as credentialing evidence. However, it never explicitly says when to prefer search_providers or providers_near instead, so the routing decision is left to inference.

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