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

Annotations already mark this read-only, idempotent, and non-destructive, so the bar is lower. The description adds meaningful behavioral context beyond annotations: it returns ranked drugs, each backed by survey sample information, and scopes the estimate to the whole U.S. population rather than a specific payer program.

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?

Three sentences, with the core purpose front-loaded and no filler. Each sentence earns its place: what the tool returns, the population scope, and how to phrase the query.

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 tool with four well-documented parameters and no output schema, the description provides enough context: it explains the return shape (ranked drugs with sample support), the population coverage, and the input style. Slightly more detail about exact output fields would be helpful, but the definition is functional and complete for selection and invocation.

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 100%, so the baseline is 3. The description reinforces the condition parameter with examples and explains the ranking/sample output, but it does not add meaningful new semantics for year, limit, or min_sample beyond what the schema already documents.

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 opens with a specific, informative purpose: mapping a medical condition to the prescription drugs Americans take, with national estimates. It clearly distinguishes itself from sibling tools like meps_conditions_for_drug by framing the query around a given condition and emphasizing whole-US-population coverage.

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 gives concrete guidance on how to ask the tool, including plain-language condition examples, and clarifies that the tool covers all payers and ages rather than only Medicare/Medicaid. It does not explicitly name alternatives or state when not to use it, so it stops just short of full exclusion guidance.

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