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

Annotations already cover read-only safety, so the description adds value by disclosing the source database, per-call cost, output content, and a concrete example. It does not discuss rate limits or authorization, but the annotation coverage lowers the burden and this description adds meaningful context beyond it.

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?

Compact and front-loaded: use cases first, then return shape, an illustrative example, source, and cost. No filler; each sentence earns its place and helps with both selection and invocation.

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 adequately explains return values through the aggregate description and the Dr. Smith example. It does not explicitly state how manufacturer_name and program_year combine, but the input schema covers requiredness and the tool is a straightforward read-only retrieval.

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 clarifies that the tool aggregates by physician or manufacturer, and the example implies manufacturer_name and program_year act as filters. It does not explicitly map each parameter to its role, so it is strong but not exhaustive.

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: 'Returns CMS Open Payments aggregates by physician or manufacturer' with payment amounts, types, and program year breakdown. The 'Sunshine Act' and 'CMS Open Payments' phrasing clearly distinguishes it from siblings like get_cms_facility_benchmark or get_cms_star_rating.

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 frames when to use: physician payment transparency risk, manufacturer relationship evaluation, and Sunshine Act compliance reporting. It does not name alternatives or when-not-to-use, so it falls just short of a 5, but the context is clear and actionable.

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