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

The description goes well beyond the readOnly/idempotent annotations by disclosing key behavioral traits: the name resolver picks a genuine NPPES match rather than a blind top hit, payments are pinned to that exact NPI, a failing source is noted rather than fatal, and the result is a transparency profile rather than a judgment. The 'verify against primary sources' caveat also sets appropriate expectations.

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 somewhat long but front-loaded and largely information-dense. It covers purpose, inputs, matching behavior, source-failure handling, and interpretation caveats. Minor promotional or redundant phrasing such as 'Premium cross-source synthesis' could be trimmed, but the content earns its place overall.

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 no output schema, the description compensates by enumerating the key returned data points for both identity and payments. It also addresses the most recent program year default, disambiguation needs, failure behavior, and the appropriate interpretation of industry payments. The tool is complex enough that this level of detail is necessary and sufficient.

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 already provides 100% parameter coverage, so the baseline is 3. The description adds meaningful context beyond the schema: it explains that last_name should ideally be combined with first_name and state, that an exact NPI overrides the name search, and that the resolver matches genuinely rather than picking a top hit. This elevates the score above baseline.

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: a one-call profile combining prescriber identity from NPPES with industry payment data from CMS Open Payments. It specifies concrete output elements (NPI, specialty, city/state, active status, payment totals, top manufacturers) and differentiates itself from single-source tools like npi_lookup or open_payments_search by emphasizing the cross-source synthesis.

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 gives clear caller guidance: provide last_name, ideally with first_name and state, or an exact 10-digit npi. It also explains that the npi overrides name search. It does not explicitly name sibling alternatives or state when not to use this tool, but the input guidance and source combination make usage context clear.

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