Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's added detail (lowest displayed price, summary, price-page slug) describes return contents, but an output schema exists, so this is largely redundant rather than genuine behavioral insight such as ordering, pagination, or class-size limits.

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?

A single sentence, front-loaded with the action and resource, with the output summary trailing. No filler or repetition.

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?

With an output schema, annotations, and a fully documented single parameter, the description covers what an agent needs to invoke it and what to expect back. The only gap is the absence of any hint about result volume or pagination for a class that could contain many drugs.

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 100% with a single 'slug' parameter, so the baseline is 3. The description restates the slug's origin via the sibling tool name, adding slight value over the schema's path-style reference (/goodrx/classes), but contributes no format or validation detail.

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 and resource ('List the drugs ... for one drug class') and names the source collection (goodrx_classes), which cleanly separates it from the sibling goodrx_classes that produces the slugs. An agent can tell what it returns without opening the 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?

It establishes the prerequisite flow by telling the agent the slug comes from goodrx_classes, which is the key routing decision versus the class-listing tool. There is no explicit 'when not to use' or mention of sibling drug-detail price tools, so it falls short of full alternative coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.