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

Annotations already establish this as a safe read (readOnlyHint=true, openWorldHint=false), so the description is free to add the operationally important context: the freshness window (checked within 48h), the reference period (previous 90 days lows), the multi-reading requirement, and the new-condition/Amazon-only scope. That is meaningful beyond the annotations, though it says nothing about result volume or rate limits.

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?

Front-loaded with the core concept, and every clause in the first sentence carries a qualifying criterion an agent would otherwise have to guess. The first sentence is dense and clause-heavy, but nothing is padding; the two follow-up sentences on return payload and filtering are short and useful.

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, the description usefully states what each deal returns (reference price, period, number of reading days), and it covers qualification criteria and filtering. Only edge details such as ordering, pagination or behavior when fewer deals exist than 'limit' are left 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 100%, so both parameters are already documented; the description only restates the *optional* nature of the name filter and adds an example-free gloss ('words in the product name'), while never mentioning 'limit'. This meets the baseline of 3 without adding real semantics beyond the schema.

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 resource ('Current verified price drops') and goes further by defining exactly what makes a drop qualify (same offer below its own 90-day low, multiple reading days, checked within 48h, new condition, Amazon re-verified). This clearly distinguishes it from get_price_history or search_products, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for pre-computed deal listings and that 'query' narrows by product name. There is no explicit when-to-use versus get_price_history or search_products, and no stated exclusions, so the agent must infer routing from the resource name alone.

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