provider_enrich

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return content (practice details, specialties, etc.) but lacks critical details: whether this is a read-only operation, potential rate limits, authentication needs, error handling, or data freshness. For an enrichment tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and front-loaded: a single sentence that efficiently conveys the core functionality and return values. Every word earns its place, with no redundant or vague phrasing, making it easy for an agent to parse quickly.

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 the complexity of provider enrichment (likely involving external data sources), no annotations, and no output schema, the description is incomplete. It lists return categories but doesn't explain the output structure, potential limitations, or error cases. For a tool with rich data returns and no structured output documentation, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, with the single parameter 'npi' documented as a '10-digit NPI number'. The description adds no additional parameter semantics beyond what the schema provides (e.g., format examples, validation rules). According to the rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description.

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's purpose: it enriches provider intelligence from an NPI number, specifying the action ('AI-enriched') and resource ('provider intelligence'). It distinguishes from siblings like provider_search (searching) and provider_payments (financial data) by focusing on enrichment. However, it doesn't explicitly contrast with drug_enrich (similar enrichment for drugs), keeping it from a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid NPI), exclusions, or comparisons to siblings like provider_search (which might return basic info without enrichment) or drug_enrich (for drug data). Usage is implied by the purpose but not explicitly stated.

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