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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds useful behavioral details: search results may combine similarly named legal entities and matching is case-insensitive. This goes beyond annotations, though it does not cover pagination or result limit behavior.

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: first clearly states purpose, second adds critical matching details. No unnecessary words, information is front-loaded and directly useful.

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 complexity (6 parameters, multiple sibling tools), the description lacks details on parameters like payment_type, minimum_amount, and pagination. It also does not help differentiate when to use this vs other open_payments tools. The output schema is present but the description should still contextualize return values.

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 description must carry the burden. It explains only the 'company' parameter behavior (case-insensitive substring, combining entities). Other parameters (year, limit, offset, payment_type, minimum_amount) are not described. The description does not fully compensate for the lack of schema descriptions.

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?

Description clearly states the action ('Search payments reported by a manufacturer or GPO') and scope ('in one CMS Open Payments program year'). It distinguishes from sibling tools like open_payments_physician or open_payments_product by focusing on payments by company rather than recipient or product.

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?

Provides partial guidance on matching behavior (case-insensitive substring, combining similar entities) but does not explicitly state when to use this tool versus alternatives such as open_payments_search or open_payments_company_history. No comparative usage advice.

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