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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior, so the description does not need to repeat those. It adds the useful hint that state/city narrow the search and are recommended, but it does not disclose behavioral details such as what happens without location filters, pagination behavior, or result limit interpretation.

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?

The description is two sentences, front-loads the main action and scope, and contains no filler. Each clause adds a useful decision-relevant detail: what is searched, what is required, and how to narrow results.

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 simple read-only search tool with four fully documented parameters and strong annotations, the description is largely sufficient for correct invocation. It provides the required parameter, optional narrowing fields, and examples. It does not describe the return shape, but there is no output schema and the purpose makes the expected result reasonably clear.

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. The description adds value beyond the schema by giving multiple concrete examples of taxonomy values ('Cardiology', 'Pediatrics', 'Nurse Practitioner') and by framing state/city as 'recommended' rather than merely optional, which helps the agent choose effective inputs.

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 is specific: it names the verb 'Find', the resource 'healthcare providers', and the selection logic 'by specialty (taxonomy description) in a location'. It is clear and maps to the tool name, but it does not explicitly contrast with sibling tools like npi_search_provider or npi_search_organization, so it stops short of a 5.

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 clearly says taxonomy is required and that state/city are optional but recommended, which gives practical usage context. However, it never mentions when to prefer this tool over the sibling NPI search tools or when not to use it, so the guidance is implied rather than explicit.

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