Deals

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

Adds substantial context beyond the readOnly/idempotent annotations: deal_ends is UTC, total is the pre-filter list size, and biggest_percent/min_discount_pct cause each page to scan the next 100 deals and return the best `limit`, with more_on_page counting the cut-off matches. That is genuine operational behavior an agent cannot get from the annotations.

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?

Dense and front-loaded: the tool's identity leads, then behavior, then the alternative. Some clauses (the 100-deal scan explanation) are tightly packed but each earns its place; nothing is padding.

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?

An output schema exists, so return format need not be described, and the description covers paging, filtering, and the sibling alternative well. It leaves minor ambiguity about how page numbering advances through the 100-deal scan window, but is otherwise sufficient for correct invocation.

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 coverage is 100%, so baseline is 3, but the description goes further by explaining the interaction between sort, min_discount_pct and paging (scan window, more_on_page) and by clarifying that total ignores min_discount_pct. It still doesn't explain how page interacts with the scan window, leaving a minor gap.

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 specific verbs and resources: in-stock discounts from the main deal list (تکنوآف) plus timed home-page deals (تکنو تایم) on page 0. An agent can distinguish this immediately from tl_category_products, tl_find_cheapest, and the other siblings.

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?

Directly answers the selection question with 'Use for "best deals right now"' and routes the category-scoped case to a named alternative (tl_category_products with sort=biggest_discount_toman), including the exact parameter value needed.

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