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

readOnlyHint=true already establishes the safe-read profile. The description adds useful behavioral detail not in the annotations (trailing '*' wildcard matching and the 2-char minimum before the wildcard, plus the API/version 'NPPES Read API v2.1'), but it omits rate limits, result caps, or pagination behavior beyond what the schema covers.

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?

Four short, front-loaded sentences with no filler; the core scope (individual providers) leads and the important eligibility constraint follows. Slightly dense but 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 an 11-parameter, fully optional, no-output-schema search tool, the description supplies the essential routing and constraint guidance. Return format is not described, but the absence of an output schema makes that a minor omission rather than a blocking gap.

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%, so the baseline is 3, but the description adds real value: the 2-char minimum before a wildcard for name fields is not stated in the per-parameter schema descriptions, and the taxonomy keyword examples reinforce the specialty filter. It does not expand on the enum-only parameters (name_purpose, address_purpose) which the schema already handles.

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+resource ('Search for INDIVIDUAL healthcare providers'), enumerates the criteria (name, specialty/taxonomy, location), and disambiguates from the sibling nppes_search_organizations via the emphasized INDIVIDUAL/NPI-1 framing. An agent can route between the two search tools without opening a schema.

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?

Explicitly instructs 'Provide at least one meaningful criterion beyond a location', a genuine usage constraint, and the location/name/taxonomy framing clarifies intended search contexts. It stops short of naming nppes_search as the generic alternative or stating when-not-to-use, so it is strong but not fully complete.

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