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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the specialty-scoped search framing and the optional-but-recommended location hint, with nothing about result counts, pagination, or the limit behavior.

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 compact sentences, front-loaded with the core action and followed by the key parameter constraint. Little wasted text, though the taxonomy examples repeat what the schema already states.

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 read-only, high-schema-coverage search tool with no output schema, the description covers the required input and the primary optional narrowing. Return format and default result handling are left unstated, but the annotations and schema make this acceptable.

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 city, state, limit, and taxonomy are all documented in the schema with examples. The description's taxonomy examples ('Cardiology', 'Pediatrics') largely duplicate the schema's own example, though the 'state and city optional but recommended' note is a small semantic addition.

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 (Find) and resource (healthcare providers) with the narrowing facet ('by specialty (taxonomy description) in a location'). This distinguishes it in spirit from name/org-oriented siblings like npi_search_provider and npi_search_organization, but it never names or contrasts those siblings explicitly.

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?

Gives useful parameter-level guidance ('Requires taxonomy... state and city optional but recommended'), which tells the agent how to fill the call. It does not say when to prefer this tool over npi_lookup, npi_search_provider, or npi_search_organization, so usage is only implied rather than routed.

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