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

The description discloses that the data is observational public CMS/NPPES records and not a clinical recommendation. It mentions the cost ($0.05/row) and that it uses the Healthparse Part D API. It does not explicitly state read-only or non-destructive nature, but the observational framing implies no modification.

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 dense paragraph that front-loads the core question ('Who is this prescriber?') and packs in all key details without fluff. Every sentence adds value, including the price and API source. It is highly concise for the amount of information conveyed.

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 no annotations and no output schema, the description covers the essential behavioral context: input parameters, optional filters, output summary fields, and data lineage. It could mention pagination or handling of missing NPIs, but it provides sufficient completeness for a lookup tool.

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?

All four parameters have descriptions in the input schema, so schema coverage is 100%. The tool description reiterates the parameter usage (e.g., name can be last-name prefix or first+last) but adds minimal new meaning beyond the schema. Baseline of 3 is appropriate.

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's purpose: to look up a prescriber by name or NPI and return NPPES identity and Part D prescribing summary. It specifies the exact outputs (specialty, location, top drug, claims, etc.) and distinguishes itself from sibling tools by being focused on prescriber identity and prescribing patterns.

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 tool explains when to use it: to find who a prescriber is and what they prescribe, with optional state and specialty filters. It does not explicitly state when not to use it or mention alternatives, but the usage context is clear and includes important caveats like 'never a clinical recommendation'.

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