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

Annotations already indicate read-only safety. The description adds value by specifying the source database, providing an example with a concentration threshold, and clarifying the aggregate nature of the data. It does not contradict 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 front-loaded with the use case, followed by return details and a concrete example. The example is somewhat lengthy but adds valuable context. Overall, each sentence contributes to understanding the tool.

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 no output schema and only three simple parameters, the description provides a solid overview including use cases, return contents, an example, and the data source. It lacks explicit parameter guidance and error behavior, but for a read-only data lookup it is reasonably complete.

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 coverage is 0%, so the description must compensate. It mentions 'by physician or manufacturer' and 'program year breakdown,' which maps to the three parameters. However, it doesn't clarify that recipient_name is required or detail parameter formats/constraints, and the phrase by manufacturer could mislead an agent into thinking manufacturer_name alone is sufficient.

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 'Returns CMS Open Payments aggregates by physician or manufacturer' with specific detail on payment amounts, types, and program year breakdown. It distinguishes itself from sibling tools by naming the CMS Open Payments Sunshine Act database and the specific use case.

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?

Explicitly states when to use: 'Use when assessing physician payment transparency risk, evaluating manufacturer relationships, or preparing Sunshine Act compliance reporting.' It does not mention when not to use or alternatives, but the use case is clearly defined.

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