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

readOnlyHint=true already tells the agent this is a safe read, so the description is not carrying the safety burden. It adds a useful behavioral detail (trailing '*' wildcard on organization_name, min 2 chars before it) and the API version, but says nothing about result caps, pagination behavior, or rate limits for a 9-parameter search.

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 tight sentences with zero padding: the capability and its entity-type scope lead, followed by wildcard syntax and provenance. Every clause earns its place and nothing is buried.

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 9 parameters, no output schema, and only a readOnlyHint annotation, the description covers the primary search dimensions (name, specialty, location) but omits what the call actually returns (NPI record shape / fields) and gives no pagination or result-limit context. Adequate but with clear gaps for a search tool of this breadth.

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 all nine parameters are already documented by the schema; baseline is 3. The description's wildcard note is essentially a restatement of the organization_name schema text and it does not clarify the relationship between address_purpose and the location filters.

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 (Search) and resource (ORGANIZATION healthcare providers, NPI-2), and enumerates concrete examples (hospitals, clinics, group practices, pharmacies, labs). The uppercase 'ORGANIZATION' plus the NPI-2 designation cleanly distinguishes it from nppes_search_individuals and nppes_lookup_npi without opening any 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?

The scope statement implies when to reach for this tool (entity-type 2 organizations rather than individuals), but no sibling tool is named as an alternative and there is no explicit when-not guidance. Usage is inferable rather than stated.

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