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

No annotations are provided, so the description carries the full burden. It usefully defines the inclusion rule (3% drop / 30-day low, 'today'), which is the core behavior, but it says nothing about result ordering, result caps, pagination, or data freshness.

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?

One front-loaded sentence with the bracket tag acting as a topic marker, and the quantitative thresholds conveyed without any padding. Nothing can be removed without losing information.

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 what is returned (ordering, how many items, time window semantics for the 30-day low) and about the optional category filter. It covers the trigger condition well but leaves the response shape and parameter role unspecified.

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 single 'category' parameter is never mentioned in the description, so it is unclear that results can be filtered by category or that the filter is optional. The enum values are self-descriptive, but the description adds no meaning beyond them.

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 a precisely-scoped resource (products whose price dropped ≥3% today or hit a 30-day low), which is clearly distinct from siblings like shop__get_product_price and shop__search_products. It does not explicitly name any sibling, so sibling differentiation is implicit rather than stated.

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 criteria imply the use case (surfacing deals/discounts) but there is no explicit when-to-use guidance or statement of when this is preferable to shop__search_products or shop__get_product_price. Usage is inferable but not spelled out.

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