open_payments_ownership

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description does not need to restate that. It adds domain context—what ownership data represents—and clarifies that the results show financial interests rather than merely payments. However, it does not disclose operational behavior such as result shape, pagination, or how undefined parameters behave, though the annotations lower the burden here.

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 three concise sentences with the core action and subject front-loaded. The phrase 'The deepest form of conflict of interest' is slightly editorial but adds useful context without bloating the text. Overall, every sentence earns its place, though it is not as taut as a two-sentence version could be.

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 core subject matter is clearly explained, and all parameters are documented in the schema. However, with no output schema and many closely related Open Payments sibling tools, the description would benefit from explicitly addressing relationship to alternatives and what the returned data contains beyond 'financial interests.' It is adequate but not complete for full agent decision-making.

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 100%, so the schema already fully documents all five parameters. The description adds no additional parameter-level meaning, but none is needed; all parameters are self-explanatory in the schema. Baseline 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 states a specific verb ('Search') and a precise resource ('Open Payments OWNERSHIP data') with clear scope: doctors with ownership/investment stakes in pharma/device companies. The framing 'deepest form of conflict of interest' and 'financial interests in the companies whose products they prescribe' clearly distinguishes this ownership-focused tool from the broader open_payments_search and other sibling Open Payments 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?

No explicit guidance is given about when to choose this tool over siblings such as open_payments_search, open_payments_by_company, open_payments_by_physician, or open_payments_summary. The description implies this is for ownership/investment data but does not say 'use this when...' or name alternatives, which is a meaningful gap given the large sibling set.

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