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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description doesn't need to repeat those. The description adds valuable behavioral context: product association is reporting-entity supplied and not proof of exclusivity, and it searches across all five CMS product slots, which extends beyond annotations.

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 two sentences with no redundancy. The first sentence conveys the core purpose and scope, and the second adds a crucial caveat. Every phrase 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?

Given the tool has 5 parameters, no schema descriptions, and an output schema exists, the description covers the main search function but omits details like accepted year ranges, pagination behavior, or the meaning of CMS product slots. It is adequate but not thorough for a tool with low schema coverage.

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 0%, so the description must compensate. It only explains the 'product' parameter by listing example types (drug, biologic, device, medical supply). The other four parameters (year, limit, offset, company) are not addressed, leaving a significant gap in semantic meaning for the agent.

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 searches general-payment records for a named drug, biologic, device, or medical supply across all five CMS product slots. The verb 'search' and resource 'general-payment records' are specific, and the scope distinguishes it from sibling tools like open_payments_company or open_payments_physician.

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 provides clear context for when to use this tool (searching payments linked to a product) and includes a caveat about association not proving exclusivity. However, it lacks explicit guidance on when not to use it or direct comparison to sibling tools, though naming implies product focus.

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