Compare FineRx prices for one package (an 11-digit NDC + quantity).
Returns the offer matrix: for each pharmacy chain x savings program, the
observed price and the date it was observed (observedAt). The cheapest offer
is flagged isLowest. Get an ``ndc`` from get_drug's packages or search flow.
| Name | Required | Description | Default |
|---|---|---|---|
| ndc | Yes | ||
| quantity | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by detailing the output structure (offer matrix with pharmacy chain x savings program, observedAt, isLowest), providing behavioral context beyond 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 concise at two sentences, front-loading the purpose and input, then efficiently describing the output. Every sentence adds essential information without redundancy.
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 simple two-parameter tool with an existing output schema, the description fully covers input format, output structure, and data sourcing. There are no missing details that would hinder correct usage.
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?
With 0% schema description coverage, the description compensates by specifying that NDC should be an 11-digit string and that quantity is required. It also clarifies that the input represents a 'package,' adding meaning absent from the schema's parameter definitions.
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 states the tool's purpose: 'Compare FineRx prices for one package (an 11-digit NDC + quantity).' It distinguishes from sibling tools like search_drugs and get_drug by focusing on price comparison for a specific drug package.
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 advises to 'Get an ``ndc`` from get_drug's packages or search flow,' providing a clear workflow context. However, it does not explicitly state when not to use this tool or list alternatives beyond the hint about sourcing the NDC.
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.
Each tool serves a distinct function: searching drugs, getting drug details, comparing prices, finding pharmacies, and retrieving dataset metadata. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_drugs, compare_prices, get_drug), making the set predictable and easy to navigate.
With 5 tools, the server is well-scoped for a drug pricing API. Each tool addresses a specific step in the typical workflow (search, details, price comparison, location, metadata), and the count is neither too small nor excessive.
The toolset covers the core workflow: search drugs, retrieve drug details, compare prices, find pharmacies, and obtain dataset info. A minor gap is that the mechanism to obtain an NDC from a drug is implied but not explicitly detailed, though the flow likely works.