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

With no annotations, the description discloses data sources, the nature of records ('as filed; not a consumer report'), handling of absent data, and pricing per call. This goes beyond basic functionality, though it could mention whether the call is read-only or idempotent.

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 a single paragraph that front-loads the core purpose and lists contents efficiently. It includes necessary disclaimers and pricing without redundancy, though it could be slightly more structured.

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?

Despite no output schema, the description thoroughly explains what data categories are included and notes that missing items are explicitly stated. It lacks details on pagination, rate limits, or result size, which would enhance completeness.

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 single parameter 'npi' is fully described in the schema as a 10-digit NPI. The tool description does not add additional context or constraints beyond the schema, 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?

The description uses a specific verb phrase 'One-call dossier' and identifies the resource 'provider NPI', listing distinct data categories. It clearly distinguishes from sibling tools that focus on specific datasets or searches.

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 implies usage when a comprehensive provider overview is needed, but does not explicitly state when to use this tool versus alternatives, nor provide exclusions or when-not-to-use guidance.

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