provider_payments

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

With no annotations provided, the description partially compensates by stating it is a lookup (read-only) and describing the output. However, it does not mention potential behavioral aspects such as rate limits, data year, or data refresh frequency. The description is adequate but not exhaustive.

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 concise with two sentences, no redundant information, and front-loads the core purpose. It efficiently conveys essential information without wasting words.

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 covers the key aspects: what the tool does, what it returns, and the data source. Given there is no output schema and no annotations, it provides a reasonable level of completeness for a simple lookup tool. However, it could be more complete by mentioning data year or pagination.

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 already well-described in the schema as a 10-digit NPI number. The description adds no extra meaning beyond the schema, so it meets the baseline for full schema coverage but does not enhance understanding.

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: looking up payments to a physician from pharmaceutical and device companies. It specifies the data source (Sunshine Act, CMS Open Payments) and what it returns (total payments, breakdown by type, top paying companies). This distinctively differentiates it from sibling tools like provider_enrich or provider_search.

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 the tool is for retrieving payment data but does not provide explicit guidance on when to use it versus alternatives, nor any prerequisites or exclusions. The context of being public domain is helpful, but without stating when not to use this tool, the agent may lack decision support.

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