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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and side-effect profile are covered by structured data. The description adds value beyond that by disclosing the full content of the returned record, which is the main behavioral unknown for a fetch. It does not cover not-found or error behavior, keeping it below 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?

A single sentence with zero filler, front-loading the action and resource before the field list. Every clause earns its place by naming either the input source or the returned data.

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 enumerates the record's contents, and with one fully documented parameter and rich annotations the definition is nearly self-sufficient. The only gap is the absence of not-found/error behavior, which matters for a lookup keyed on an external identifier.

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 parameter already has a description, so the baseline is 3. The description improves on it by explaining where the id comes from ('returned by search') and that any valid 10-digit NPI works, clarifying provenance and accepted input beyond the schema's bare 'The 10-digit NPI.'

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 ('Fetch the full CMS registry record for one NPI') and enumerates the returned content (status, name, taxonomies, addresses, dates), so the agent knows exactly what it gets back. It references the 'search' sibling as the source of the id, but does not distinguish itself from the similarly named lookup_npi, verify_npi, or check_npi_status, so sibling differentiation is incomplete.

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?

Implies usage by saying the id can be 'the id returned by search, or any 10-digit NPI', which gives a concrete entry condition. However, it never states when to prefer this over lookup_npi, verify_npi, or check_npi_status, nor any exclusions or prerequisites, leaving the agent to infer the boundary.

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