Current deals and discount codes

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds meaningful behavior beyond that: sort order, that pink_box_ends_in_seconds is a countdown, that each section's tag feeds kh_browse, and that the voucher is redeemed at checkout with its terms in voucher.text.

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-loads the core purpose, then usage, then output-field hints; every sentence carries information. It is dense and slightly scattershot in mixing output semantics with usage guidance, but there is no filler.

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 shape need not be explained, yet the description still clarifies the non-obvious output fields (pink_box_ends_in_seconds, section tag, voucher.text). Combined with annotations and 100% param coverage, an agent has everything needed to call and interpret it.

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% with a single documented 'limit' parameter (default 30, max 100). The description adds no further semantics about limit, so the baseline 3 applies when the schema carries the whole burden.

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 featured deals from the Khanoumi home page'), covers both the daily pink box and the pop-up campaign voucher, and is clearly distinct from siblings like kh_search or kh_browse. The ordering guarantee ('biggest discount first') further narrows what this tool is.

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 an explicit use trigger ('Use for "what's on sale" / "best discounts today"') and routes product-level drill-down to the sibling kh_browse(tag=...). It does not state when to prefer kh_search or kh_find_cheapest over this tool, so the exclusion side is incomplete.

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