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

Annotations already declare readOnlyHint and openWorldHint, so safety and openness are covered. The description adds what the results contain (lowest displayed price, summary, price-page slug), but since an output schema exists, this return-value detail is largely redundant with structured data rather than new behavioral context.

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 front-loaded sentence carrying purpose, input provenance, and return contents with no wasted words.

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 annotations covering safety and an output schema covering the return shape, the description supplies everything needed to call it correctly. The only minor gap is the lack of explicit sibling disambiguation.

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 coverage is 100% with a single parameter whose description already identifies it as a condition slug from /goodrx/conditions. The description restates the same source without adding format, validation, or example details, so baseline 3 is appropriate.

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 (medications) with a clear scope constraint ('for one condition'), and names the sibling source goodrx_conditions for the input. An agent can distinguish this from goodrx_conditions and goodrx_drug_prices without opening a 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?

The phrase 'condition slug from goodrx_conditions' tells the agent where the required input comes from, which is actionable prerequisite guidance. It stops short of explicitly contrasting with similar siblings like goodrx_drug_prices or goodrx_drug_options, so the when-not-to-use case is left implicit.

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