List GoodRx drug comparisons grouped by health topic and get slugs for head-to-head pages. Use it to find and link relevant drug comparison data.
List GoodRx drug comparisons. Returns GoodRx's head-to-head drug comparisons grouped by health topic, with slugs for /goodrx/comparison.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose the useful structural facts that results are grouped by health topic and carry comparison slugs, but says nothing about pagination, ordering, or rate limits. For a zero-parameter read-only list endpoint that is acceptable but not rich.
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?
Two tight sentences with zero waste; the core purpose is front-loaded and the return detail follows.
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 zero-param, no-output-schema listing tool the description covers what an agent needs to invoke it, but it leaves the ambiguity with the near-identical sibling goodrx_comparison unresolved, which is the one gap that matters here.
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?
The tool takes zero parameters, so there is no parameter meaning for the description to add. The baseline for a no-param tool is 4.
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?
States a clear verb ('List') and resource ('GoodRx drug comparisons'), plus the return shape (head-to-head comparisons grouped by health topic, with /goodrx/comparison slugs). It does not, however, differentiate itself from the sibling goodrx_comparison (singular), leaving the agent unable to tell the two apart from the description alone.
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 only describes what is returned; it never states when to call this versus goodrx_comparison, goodrx_conditions, or the other goodrx_* list tools. No alternatives or exclusion conditions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.