compliance_search_npi_by_name

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

Discloses read-only, no side effects, idempotent, US only, up to 10 matches, 24-hour cache. With no annotations, the description fully covers behavioral traits.

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 thorough but slightly verbose, with clear structure. The inclusion of the feedback instruction adds some length but is contextually useful.

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?

Covers purpose, parameters, output, usage guidelines, behavioral traits, cache, and source. Despite an output schema, it still describes return fields, making it complete for a search tool.

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 coverage is 0%, but the description explains each parameter's purpose, requirements, and examples (e.g., 'state: Two-letter US state code e.g. CA. Optional.'), adding significant meaning beyond the schema.

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 clearly states the tool searches the NPPES NPI Registry by provider name with optional filters, and differentiates from the sibling tool compliance_fetch_npi_provider by noting it is for when you do not have the NPI number.

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 when to use this tool ('when you do not have the NPI number') and when to use the alternative ('compliance_fetch_npi_provider instead when you have the exact 10-digit NPI'). Also includes a feedback fallback mechanism.

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