get_promotions

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

With no annotations provided, the description carries full burden. It discloses that the tool returns promotion name, discount, validity dates, and applicable stores, implying a read-only operation. However, it does not mention pagination, default ordering, or any limitations, leaving moderate gaps.

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: first states purpose, second lists filters and output, third gives example use cases. Every sentence adds value, and the key information is front-loaded. No redundancy or fluff.

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 tool's complexity (4 optional parameters, no output schema, no annotations), the description covers purpose, filtering, output fields, and example queries. It does not discuss pagination, error handling, or defaults, but for a list tool these omissions are acceptable.

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 baseline is 3. The description paraphrases the parameters (filter by chain, keyword, store ID, days until expiry) but adds no new meaning beyond the schema's existing field descriptions. It does not introduce additional nuance or examples for parameter values.

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 lists promotions with specific verb ('List'), resource ('current promotional deals'), and includes filtering options. It distinguishes from siblings by focusing on promotions rather than stock (find_stock) or products (get_product), and explicitly mentions use cases like 'what is on sale this week?'.

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 provides explicit example queries such as 'any Migros deals on cheese?' or 'promotions ending today', giving clear when-to-use guidance. However, it doesn't explicitly state when not to use or contrast with alternatives like search_products or find_stock, which would further improve clarity.

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