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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful operational context absent from structured fields: the authoritative source (CMS NPI Registry) and the billing model ($0.01 USDC per call via x402, charged only on success). It does not describe failure modes when no match is found, 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?

Two tight sentences: capability and scope front-loaded, then source and price as trailing logistical detail. Every clause carries information; nothing is redundant.

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, the description usefully names the fields a verification returns, so an agent knows what comes back. Inputs are fully covered by the schema and safety by annotations. Missing only guidance on matching behavior when multiple providers share a name.

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 description coverage is 100%, so the schema already documents all five parameters, and two of them (first_name, last_name) have tautological descriptions. The description adds no syntax, format, or combination guidance for the inputs, so the baseline of 3 applies.

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 (verify) and resource (US healthcare provider or organization), and enumerates the verified attributes: NPI status, name, credential, specialty and practice location. The healthcare-provider resource is clearly distinct from all siblings, which cover vulnerabilities, motor carriers, recalls, SEC filings, etc.

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?

Usage is implied by the verb 'verify' and the CMS source, but there is no explicit when-to-use, when-not-to-use, or named alternative among the sibling lookup tools. Context is inferable but never stated.

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