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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the useful scope detail that this is US-only NPI registry data, but omits behavior that matters here: default match logic across the 13 optional filters, whether an unfiltered call returns everything (0 required params), ranking, and rate/volume limits.

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, zero filler, with the searchable criteria stated first and the return type second. Every clause earns its place.

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?

Missing: whether any criteria are mandatory, how criteria are combined (AND vs OR), ordering of results, and total-count behavior for paging — all relevant for a 13-parameter, zero-required search tool with no output schema. The one-line 'Returns NPI registry records' is not enough to tell an agent what a result object contains.

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 92%, so the schema already explains nearly every parameter, including the specialty taxonomy mapping and paging. The description adds essentially nothing beyond restating that same field list, which is a reasonable baseline-3 case where the schema does the work.

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 and resource (find US clinicians or healthcare organizations) and enumerates the searchable dimensions, plus names the return type (NPI registry records). It does not reference the sibling doctor_npi_lookup, so an agent gets no explicit signal about how this search differs from that lookup.

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?

Usage is only implied by the field list and the 'within a radius of a ZIP code' phrasing, which hints at the originZip+radiusMiles pairing. There is no when-to-use vs. doctor_npi_lookup guidance, no statement of whether at least one filter is required, and no explanation of how multiple criteria combine.

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