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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond that: it identifies the data source (ASCA and CMS 2024 composite), the per-call cost ($0.02 USDC), and the nature of the returned metrics. No contradiction with 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 usage context, then states outputs, provides an illustrative example, and closes with source and pricing. It is reasonably concise and every sentence adds useful information, though the example is a bit detailed.

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?

For a simple read-only benchmark tool with two optional string parameters and no output schema, the description covers purpose, outputs, source, pricing, and usage scenarios. However, it lacks parameter value guidance and any description of the returned data structure, leaving an agent to guess valid state and specialty inputs.

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 mentions 'by specialty' and gives 'Orthopedic' as an example specialty, but it never explains the 'state' parameter, valid values, formatting, or whether parameters are optional. This is a significant gap for two undocumented string parameters.

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 states a specific output ('cost per case medians and revenue mix percentages by specialty') tied to a clear resource (ASC financial performance). It also gives concrete use cases and an illustrative example, making it easy to distinguish from the many generic benchmark siblings.

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?

It explicitly says 'Use when benchmarking ASC financial performance, evaluating an ASC acquisition, or preparing an administrator board report.' This provides clear context for when to call the tool, though it does not name alternatives or state when not to use it.

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