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

Annotations already declare this is a safe, non-destructive read, and the description adds substantial behavioral context: return fields, 90-day lowest price, normalized unit_price format and absence semantics, affiliate/source disclosures, and medicine compliance notices. It also scopes results to German online shops and makes clear there is no medical advice.

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 purpose is front-loaded, and the remaining sentences pack necessary return, pricing, disclosure, and compliance details without repetition. Despite being dense, every clause 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?

There is no output schema, so the description carries the burden of explaining return values and it does so adequately: price, shipping, delivery, stock, link, unit_price, disclosures, and compliance_notice. Combined with annotations covering safety, the definition is complete enough for correct invocation.

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%, so the baseline is 3. The description still adds useful domain meaning beyond the schema by explaining that a pack is a pack-size label that may contain several PZNs, such as original and reimports, and by reinforcing product_key provenance.

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 states a specific verb and resource: listing current offers for one product, optionally narrowed to one pack. It explicitly ties product_key back to search_products and defines what each offer contains, so an agent can distinguish it from the sibling search tool 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 clearly establishes the prerequisite that product_key comes from search_products and explains when the optional pack_size applies. It does not explicitly state exclusions or compare against any alternative offer-listing tool, but the usage context is clear.

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