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

Given no annotations, the description carries the full burden. It discloses the data source (public, no PHI), returned fields, and the OIG-LEIE exclusion flag. However, it does not explain behavior when both npi and other parameters are provided, or how default limit applies, which are minor gaps.

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?

Three sentences, no wasted words. Front-loaded with the primary action and quickly enumerates inputs and outputs. Every sentence adds value.

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 6 parameters, no output schema, and no annotations, the description is largely complete: it covers purpose, inputs, and output fields. It omits details like error handling or pagination, but for a lookup tool the provided context is sufficient for most use cases.

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 83%, so the baseline is 3. The description adds value by clarifying the two usage modes (by NPI vs. by specialty+state with optional fields), which the schema alone does not convey. This extra context raises the score.

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 clearly states the tool looks up US healthcare providers from the CMS NPPES registry, specifying two search modes (by NPI or by specialty+state with optional name/city) and lists returned fields. This distinguishes it from siblings like fda_enforcement and screen_exclusion.

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 explains how to use the tool (two modes) but does not explicitly state when to use this tool versus alternatives like new_exclusions or fda_enforcement. The phrase 'Public data only — no PHI' provides a constraint but no comparative guidance.

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