Find the nearest pharmacy locations to a US ZIP code, per chain.
``zip`` is a 5-digit US ZIP. Optional ``chains`` is a comma-separated list of
chain codes (e.g. "walgreens,publix"); default is all chains. ``limit`` caps
locations per chain. Coordinates are OpenStreetMap-sourced (ODbL).
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes | ||
| limit | No | ||
| chains | No |
| 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, indicating safe, non-destructive behavior. The description adds value by noting that coordinates are OpenStreetMap-sourced (ODbL), providing data provenance context. No contradictions.
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 three sentences, front-loads the main purpose, and includes necessary parameter details without verbosity. Every sentence adds value.
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 existence of an output schema, the description doesn't need to detail return values. It covers parameters, defaults, and data source. It could mention sorting by distance or error handling, but it is largely complete for its purpose.
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 carries the full burden. It explains each parameter: 'zip' is a 5-digit US ZIP, 'chains' is a comma-separated list with an example and default, 'limit' caps per chain. This goes well beyond the schema's type/default info.
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 uses a specific verb-resource combination ('Find the nearest pharmacy locations') and scopes it to a US ZIP code per chain. It clearly distinguishes from sibling tools like search_drugs or compare_prices, which focus on drug information or pricing, not location.
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 purpose is clear enough that an agent can infer when to use it (geographic pharmacy search). However, there is no explicit guidance on when not to use it or mention of alternative tools, which would push it to a 5.
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.