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

Annotations already mark this as read-only and non-destructive. The description adds meaningful context beyond that: it identifies the data source (CMS VBC program data composite), discloses a per-call cost of $0.02 USDC, and illustrates the kind of analytical output with a concrete example. This is useful behavioral and practical information not available in structured fields.

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 compact and front-loaded, starting with use cases, then output, then an example, source, and cost. Each sentence adds information; the example is valuable for setting expectations. It could be slightly tighter, but it stays efficient.

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 and only 25% parameter coverage, the description does a decent job of explaining what the tool returns and why to use it. However, it leaves important context unstated: how optional parameters like bed_size and specialty filter the data, and what happens when they are omitted. For a 4-param tool, this is a meaningful gap.

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 only 25%: only current_vbc_revenue_pct has a description. The tool description mentions program types like MSSP, BPCI, and MIPS but never explains the meaning or role of bed_size, specialty, or how parameters affect the result. Since the schema is weak, the description needed to compensate and does not.

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 verb and resource: benchmarking VBC contract performance, assessing FFS-to-VBC transition readiness, and preparing population health strategy presentations. It names concrete output content (MSSP ACO savings rates, BPCI episode costs, MIPS quality signal medians), which clearly differentiates it from the many generic sibling benchmark tools.

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 gives explicit when-to-use scenarios: benchmarking VBC contract performance, transition readiness, and population health strategy. It does not name alternative sibling tools or explicitly state when not to use it, but the provided context is clear enough to guide an agent.

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