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

Annotations declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds behavior beyond annotations by noting it's a 'static model derived from published 340B savings ranges,' and the example illustrates the nature of outputs (e.g., $287/adjusted patient day). This adds context about data origin and output style, earning a 4.

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: usage, returns, and an illustrative example plus source. Each sentence carries useful information, but the example is somewhat lengthy and could be trimmed. Still, it's well-structured and front-loaded with the use case.

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?

The description covers usage, outputs, an example, and data source, but it lacks parameter explanations and output structure. Given no output schema and 5 undocumented parameters, the description is not fully complete, though it provides a workable understanding for a read-only benchmarking tool.

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 has 0% description coverage, so the description must compensate, but it does not describe any of the five parameters (state, bed_size, etc.). It mentions 'by bed size' only as an output dimension, not how the input is used. This leaves parameter semantics completely unexplained, so a low score is warranted.

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 what the tool does: 'Returns drug cost per adjusted patient day, 340B savings opportunity from published savings ranges, specialty drug drivers, and GPO targets by bed size.' This specific verb+resource distinguishes it from sibling benchmark tools by focusing on pharmacy spend, and the context 'benchmarking hospital pharmacy costs' clarifies its niche.

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?

Provides an explicit use case: 'Use when benchmarking hospital pharmacy costs or building a pharmacy cost reduction strategy for a board presentation.' While it doesn't mention alternatives, it clearly establishes when to use the tool, achieving 'clear context, no exclusions' per the rubric.

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