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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered externally. The description adds context about ranking logic and spending outputs, which is useful, but it does not disclose behaviors like result limits, year fallback, or how open-world data changes might affect results. It does not contradict the 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 two sentences with no filler: the first states the dataset and ranking, the second restates the intended user question. It is front-loaded with the most important information and every sentence earns its place.

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?

Given the tool has no output schema, the description usefully indicates that results are ranked drugs with total and out-of-pocket spending. It also references a year scope. It does not explicitly mention that results can be ordered by fills or limit size, but those are covered by the parameter schema, so nothing critical is missing for this simple read-only 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 description coverage is 100%, so the parameters year, limit, and order_by are already fully documented in structured form. The description adds no parameter-specific details beyond referencing 'a given year,' so it provides no extra semantic value beyond the schema baseline.

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 identifies a specific resource and task: returning the most-used prescription drugs in the US, ranked by estimated number of people who filled them, with spending figures. It also answers the implied question 'what are the most common medications?' However, it does not explicitly contrast itself with sibling tools like meps_drugs_for_condition or meps_conditions_for_drug, so the differentiation is implicit rather than stated.

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 implies when to use the tool: when someone asks about the most commonly taken medications in America for a given year. It provides no explicit guidance about when not to use it or which sibling tool to prefer, such as condition-specific drug lookups, so usage guidance is present but only at the level of implication.

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