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

Annotations already indicate read-only and non-destructive behavior. The description adds valuable context by detailing the exact data points returned (denial rates, prior auth burden, payer mix commentary), providing an illustrative example with real numbers, and citing the data source. This goes beyond the annotation's simple safety profile.

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 three sentences, front-loaded with use cases, and each sentence earns its place: purpose, output summary, and a concrete example with source attribution. No word is wasted, and the information density is high.

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 only two optional parameters and no output schema, the description provides sufficient detail about the expected content and source. It tells the agent what kind of data to expect and gives a realistic example. It does not describe potential response format or edge cases, but for a read-only intelligence tool with optional filters, the coverage is adequate.

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?

The input schema has zero parameter descriptions and no enums, so the description carries the burden. It implies that 'payer_name' filters by payer and 'specialty' filters by specialty, but the mapping is implicit rather than explicit. The example includes payer names but does not clearly explain how each parameter affects the output, leaving some ambiguity for an agent deciding whether to pass optional arguments.

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 explicitly states the tool's purpose: benchmarking payer performance, denial management, and board reporting. It names specific outputs (denial rates by payer, prior authorization burden by specialty, payer mix commentary) and is clearly distinct from sibling benchmark tools focused on facilities, drugs, or providers.

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 opens with 'Use when benchmarking payer performance, building a denial management strategy, or preparing revenue cycle board reporting,' which gives clear, concrete scenarios for when to invoke this tool. It does not explicitly name alternatives, but the use-case framing is sufficient to guide selection among the many sibling tools.

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