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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds real value by naming the data source (CMS/Sunshine Act), the dataset scale (15M+ records per year), and the shape of returned fields. It stops short of noting pagination limits or result ordering.

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?

Three sentences, well front-loaded: identity and scope first, filters second, return shape and scale last. No filler, though the returns list slightly duplicates what could live in an output schema.

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?

With no output schema, the description usefully enumerates return fields and notes data volume, giving the agent enough to judge coverage. Minor gaps remain around default year behavior interaction and result limits, though those live in the parameter descriptions.

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 every parameter is already documented with examples and constraints. The description merely restates the filterable dimensions (company, doctor surname, state, specialty, year) without adding syntax, matching behavior, or interaction rules.

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?

States a specific verb and resource -- searching CMS Open Payments general payments under the Sunshine Act -- and names the covered entity types (pharma/device companies paying doctors and teaching hospitals). It does not, however, distinguish itself from siblings like open_payments_by_company, open_payments_top, or open_payments_state_totals, which an agent would need to route between.

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 when-to-use guidance, no prerequisites, and no named alternatives among the many open_payments_* siblings. The 'general payments' scope implicitly hints it is not the research-payments tool, but the agent is left to infer that.

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