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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds a genuinely useful interpretation caveat — ranking by discount is not a quality/value guarantee — but says nothing about result format, pagination behavior, or how ranking ties are handled.

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 front-loaded sentence with the ranking rule first and the caveat second; zero filler. Brevity is appropriate for a definition whose parameters are fully schema-documented.

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 8 optional parameters, no output schema, and an open-world data source, an agent would benefit from knowing how multiple filters interact and what a result record looks like. Annotations and full schema coverage carry most of the load, but the description leaves these behavioral questions unanswered.

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% across all 8 parameters, so the schema already documents page, limit, query, store, country, category, max_price, and min_discount. The description adds no parameter-level meaning (e.g., how filters combine), so the baseline 3 applies.

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 (find) and resource (deals) plus the ranking criterion (percentage discount), which distinguishes it from a plain search. It does not name any sibling (search_deals, compare_deals) to sharpen the boundary, so it falls short of a 5.

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?

There is no guidance on when to choose this over search_deals, compare_deals, or get_store_offers, and no mention of prerequisites or filter-combination behavior. Usage must be inferred entirely from the name and ranking phrase.

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