List featured brand-name drugs on GoodRx and return each medication's price-page slug for pricing lookups.
List GoodRx featured brand-name drugs. Returns the brand-name medications GoodRx features on its brand-name drugs page, with price-page slugs.
| 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?
No annotations exist, so the description carries the burden, but for a zero-parameter read-only listing this is a light load. It usefully discloses that results include price-page slugs, which is real return-content context, yet it says nothing about pagination, size, or ordering.
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 short sentences, front-loaded with the purpose. The second sentence partially restates the first before adding the new detail about price-page slugs.
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 parameterless list endpoint with no output schema and no annotations, the description covers what the tool returns and where the data comes from. Missing only routing guidance relative to sibling goodrx tools.
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 nothing for the description to document. Baseline 4 applies.
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 specific verb ("List") and resource ("GoodRx featured brand-name drugs") and clarifies the scope as the brand-name drugs page. It does not explicitly contrast with close siblings like goodrx_drugs or goodrx_conditions, so an agent must infer the distinction.
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?
No guidance on when to choose this over the many other goodrx_* tools (goodrx_drugs, goodrx_conditions, goodrx_drug_prices). Usage is only weakly implied by "featured brand-name drugs".
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.