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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered and the description does not contradict it. The description adds useful context like the 15M+ records per year and the type of data returned, but it does not disclose matching behavior, pagination, sorting, or rate limits. This is adequate but not rich.

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 tight sentences with no filler. It front-loads the core action and resource, then lists filters, return fields, and scale. Every sentence earns its place.

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?

There is no output schema, so the description's summary of return fields is valuable. Annotations cover the safety profile. However, in a large sibling set with many open_payments_* tools, the description does not clarify how this general search relates to the aggregate or specialized variants, leaving a meaningful selection gap.

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 parameters are already documented in the schema. The description restates the main filters (company, doctor surname, state, specialty, year) and adds a little semantic grouping, but it does not add significant meaning beyond what the schema provides.

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 a specific verb (Search), a specific resource (CMS Open Payments general payments under the Sunshine Act), and the domain (pharma/device payments to doctors and teaching hospitals). It also narrows scope to 'general payments,' which helps distinguish it from research/ownership variants, though it does not explicitly name or contrast sibling 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 guidance is given on when to use this tool versus the numerous open_payments_* siblings, such as open_payments_by_company, open_payments_state_totals, or open_payments_research. The filtering language implies a general-purpose record search, but the agent must infer when this is the right choice and when an aggregate or specialty-specific sibling is better.

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