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

With no annotations, the description carries full burden. It explains the drug_category selection logic, the return structure (one row per NPI with claim rollups), and the non-consumer-report nature. It does not detail pagination but that is schema-specified.

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, front-loaded paragraph with no wasted words. It covers purpose, usage, key parameters, and pricing efficiently.

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?

The description explains the core logic and return format, but could mention ordering (implied by ranking) and that pagination is via limit/offset. Given no output schema, it is fairly complete.

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 71%; the description adds meaning beyond schema by explaining how drug_category drives min_claims and sorting, and that performance_year defaults to 2024. It clarifies the state parameter but doesn't elaborate on limit/offset.

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 screens Medicare Part D prescribers by specialty, state, and claim volume, targeting a pharma/device team. It distinguishes from sibling tools by focusing on Part D prescriber roster, but does not explicitly contrast with similar prescribers_partD* tools.

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 for targeted outreach but does not explicitly state when to use or avoid this tool, nor does it mention alternatives. The pricing and data type hint at appropriate contexts.

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