List every brand/generic label, form, dosage, and quantity GoodRx prices for one drug slug; returns the option details and the default prescription. Use before goodrx_drug_prices to pick a valid prescription configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that it returns option details plus the default prescription, which is useful beyond the annotations, though it says nothing about auth, rate limits, or pagination.
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 tightly packed clauses with zero waste: the first front-loads what is listed and returned, the second gives the routing/sequencing instruction. 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?
For a one-parameter read tool with an output schema present, the description covers purpose, return shape, and usage sequencing adequately; return values need not be detailed since an output schema exists.
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 0%, so the description must carry the param. It clarifies that the single input is a 'drug slug' (narrowing the meaning beyond an untyped string), but does not explain where to obtain the slug or its format. Marginal value over the schema.
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 (brand/generic label, form, dosage, quantity GoodRx prices) scoped to one drug slug. It explicitly distinguishes itself from the sibling goodrx_drug_prices, so an agent can tell the two apart without opening either schema.
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?
Explicitly names the alternative (goodrx_drug_prices) and the sequencing condition (use this BEFORE it) plus the reason (to pick a valid prescription configuration). This is a direct when-to-use instruction rather than an implied one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
