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

With no annotations, the description carries the behavioral disclosure burden. It usefully notes that the service is free and returns only the top 3 matches, but it does not explain permissions, rate limits, matching behavior, or error handling.

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 tightly packed sentence with the most important facts front-loaded, including "FREE" and the lookup modes. It is efficient, though the terse colon-list style leaves some ambiguity about parameters.

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?

Given five parameters with zero schema descriptions, no annotations, and no output schema, the description is not complete enough for reliable invocation. It omits organization handling, first/last name distinction, and behavioral details an agent would need to choose correct inputs.

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 0%, so the description must compensate for five undocumented parameters. It mentions NPI, state, and a vague "name" field, but does not clarify first_name vs last_name vs organization, nor which combinations are valid.

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 states a clear verb and resource: look up a US healthcare provider by NPI or name with state. It also names useful return fields and a result cap, but it does not distinguish this tool from sibling tools such as provider_search or batch_verify.

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 it is for provider lookups, but it gives no explicit when-to-use guidance, no when-not-to-use cases, and no comparison to sibling tools like provider_search or batch_verify.

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