Current deals

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

Annotations already cover read-only, idempotent, and open-world. The description adds meaningful context beyond annotations: ranking rule (biggest discount first), in-stock filtering, returned fields (discount_pct, price_before_discount, deal_ends), timezone (Tehran), and store-specific behavior. It doesn't disclose pagination size or sort overrides, but the annotations lower the bar and the description meaningfully supplements them.

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?

Three sentences, front-loaded with the key action and scope, then field-level detail, then a use-case cue. No filler; each sentence contributes relevant 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?

Given annotations and a 100%-covered schema plus an output schema, the description is nearly complete. It covers ranking, filtering, returned fields, timezone, and store variants. Minor gaps remain around pagination and sort override interactions, but the essentials for correct invocation are present.

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 all six parameters are already documented in the schema. The description reinforces the store semantics and note about Tehran time, but adds little beyond the schema. Baseline 3 is appropriate given the schema's completeness.

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 and resource ('List today's Incredible Offers (flash deals)'), and adds discriminating scope: biggest discount first, in-stock only. An agent can distinguish this from dk_search (general search) and dk_find_cheapest (price-focused) without opening the schema.

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?

Gives a clear usage trigger ('Use for "best discounts right now"') and a store variant condition. It does not explicitly name which sibling to use for non-deal searches, but the implicit contrast with dk_search is reasonable. Lacks explicit when-not-to-use guidance.

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