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

No annotations are provided, so the description carries the full disclosure burden. It usefully defines the selection logic (3% drop / 30-day low), but says nothing about result ordering, result limits, whether the list is paginated, or whether the category filter is optional, which are relevant for a dynamic daily-deal listing.

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 tightly written sentence preceded by a short source tag; the threshold criteria are front-loaded and nothing is redundant. Appropriate size for a simple listing tool.

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 no output schema and no annotations, the description should say more about the returned shape (fields, count, ordering) and the role of the category filter. It adequately conveys the selection rule but leaves an agent guessing about the response and filtering behavior.

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% and the description never mentions the 'category' parameter at all. Although the ten enum values are self-explanatory in the schema, the description does no work to clarify whether category is an optional narrowing filter or how it interacts with the deal criteria.

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 names a specific verb+resource (list price-drop products) and pins down the exact qualification criteria: a >3% drop today OR a 30-day new low. That precision distinguishes it from generic siblings like shop__search_products and shop__get_product_price without needing to name them.

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 filtering rule implies when the tool is useful (surface deals/new lows), but the description never states when to prefer it over shop__search_products or how to combine it with shop__get_product_price. Usage is inferable rather than stated, with no exclusions or alternatives.

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