compliance_fetch_npi_provider

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

States read-only, no side effects, idempotent, US only, 24-hour cache, and verified source. Does not mention rate limits, but overall very transparent for a simple tool.

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?

Dense yet well-structured: purpose, safety, param details, usage guidelines, source/cache, feedback. Every sentence adds value.

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?

Given single parameter and output schema existence, description explains return fields, cache, and feedback. Complete for a lookup 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 description adds critical detail: format (10-digit, no dashes/spaces), example, and requirement 'Required'. Compensates adequately.

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?

Clearly states it fetches NPI provider details by NPI number. Distinguishes from sibling compliance_search_npi_by_name by specifying when to use each.

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 says when to use this tool (exact NPI) and when to use alternative (name search). Provides format instructions and feedback mechanism.

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