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

No annotations, so the description carries the burden, and it does disclose the returned payload in concrete terms: registry record plus Open Payments total, Medicare billing, OIG exclusion, clinician record, facility enrollments, and claimed-page details, each with its page section. It also explains that the result's url is the citation target. It does not say what happens on an unknown or malformed NPI, which keeps it short of a 5.

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?

Three sentences, front-loaded with the trigger condition, then scope, then return value. The parenthetical inventory of data sources is long but each item is informative rather than filler; slightly compressed, it would be a 5.

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?

With no output schema and no annotations, the description compensates by enumerating the returned sections and explaining how to cite the result. For a one-parameter read tool this is sufficient for correct invocation and downstream 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?

Schema coverage is 100% and the single npi parameter is already documented as a 10-digit identifier, so the description adds nothing about format, validation, or accepted variants. Baseline 3 applies when the schema does all the work.

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?

States a specific verb and resource ('One provider by NPI') and immediately distinguishes itself from search_providers, which returns candidates rather than a single resolved record. The agent knows exactly what comes back before opening the schema.

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 names both trigger conditions: the question names an NPI, or search_providers has already identified the right person. This is a genuine two-step routing instruction naming the sibling and the condition that selects it.

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