Backwork

backwork_coverage_lookup is an explicit aggregator that states it combines code lookup, policy evidence, prior-auth checks, claim-risk validation and jurisdiction comparison in one workflow, directly overlapping backwork_claim_validation, backwork_prior_auth_research and backwork_policy_research. Similarly, policy_research's 'reviewing policy changes' overlaps compliance_review's queue review. The detailed 'Use it when' guidance mitigates this, but an agent asking 'does this code need prior auth?' could reasonably pick either coverage_lookup or prior_auth_research.

All six tools follow a single predictable pattern: backwork_ prefix plus snake_case noun_phrase (claim_validation, compliance_review, coverage_lookup, drug_formulary_research, policy_research, prior_auth_research). No style mixing whatsoever, and names map clearly to their domains.

Six workflows for a broad domain (claims, compliance, coverage, formulary, policy, prior auth) is well-scoped. Descriptions indicate deliberate consolidation of endpoint-shaped calls into workflow tools, so each tool earns its place without excess granularity.

The surface covers the core research lifecycle: coverage lookup, claim-risk validation, policy search/compare, prior-auth checks with background research jobs, formulary evidence, and compliance queue review. Gaps are mostly intentional (no claim submission, no PHI/member-level lookup) and the read-only compliance tool has no queue-update action, which is a minor limitation.