open_payments_by_physician

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

The description adds 'Pre-aggregated totals' beyond the readOnlyHint annotation, informing that results are summary data. However, it does not disclose other behavioral aspects like performance or scope limitations beyond years.

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?

Two sentences efficiently convey the tool's purpose and behavior. No redundant or verbose language; every word 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?

Given the tool's simplicity (one optional parameter, no output schema, readOnly annotation), the description fully covers what an agent needs to know: what the tool returns and its aggregated nature.

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 input schema has 100% coverage for the single 'limit' parameter with a clear description. The description adds no further parameter meaning beyond what the schema provides, which is adequate but not exceptional.

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 action ('Get'), the resource ('payments grouped by individual physician'), and the scope ('across all years'). It effectively distinguishes this tool from siblings like open_payments_by_company or open_payments_by_hospital.

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 indicates this tool provides aggregated totals per physician, implying it is appropriate for queries about overall payments to individual doctors. It does not explicitly state when not to use it or mention alternatives, but the context is clear enough for an agent to infer usage.

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