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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds two useful pieces of context beyond the annotations: that the data is "public" (no auth/credential requirement) and which fields are returned (name, specialty, address, entity type), partially compensating for the missing output schema.

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?

A single front-loaded sentence with zero filler; the resource, the lookup key, and the returned fields all appear in the first clause. Nothing needs to be trimmed and nothing is buried.

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?

For a one-parameter read tool with full annotation coverage, the description supplies what's missing from structured data: the returned field set. It omits only edge behavior (e.g., what happens when the NPI is unknown or invalid), which is a minor gap.

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% and the only parameter's description ("10-digit NPI number") is duplicated verbatim from the schema. The description adds no format, validation, or sourcing detail beyond what the schema already provides, so baseline 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?

"Public profile for a single provider" names the resource and the retrieval key (10-digit NPI), and "single provider" implicitly contrasts with the sibling find_providers search tool. It lacks an explicit verb (get/list) and never names the alternative, so differentiation is inferable rather than stated.

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 phrase "by 10-digit NPI number" implies the precondition for use (you must already know the NPI), but there is no explicit when-to-use guidance and no mention of find_providers as the alternative when only a name is known. Usage is implied, not stated.

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