Current deals

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

Annotations only declare readOnlyHint=true; the description adds the result ordering (biggest discount first) and explains that ends_in_seconds is the remaining time in the current offer period, which is real behavioral context with no output schema to carry it. It doesn't mention pagination or result-count behavior, so it stops short of full transparency.

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 short sentences, front-loaded with the core action and ordering, then trigger phrases, then sibling routing. Every sentence carries information and there is no 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?

With no output schema, the description helpfully clarifies one return field (ends_in_seconds) and the sort order, which is enough for an agent to call and interpret results. Minor gaps remain around pagination or whether the list is capped beyond the limit parameter.

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?

There is a single parameter (limit) whose schema coverage is 100%, so the schema already documents it fully. The description adds nothing about limit usage, which is the expected baseline for a fully-covered 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?

States a specific verb and resource (list products on the discount page), plus scope ('right now') and ordering ('biggest discount first'). It explicitly separates itself from mk_search/mk_browse for keyword- or category-scoped discounts, so an agent can distinguish it without opening any 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 direct trigger phrases ('what's on sale' / 'best discounts today') and names the alternative tools with the condition that selects them (discounts inside a keyword or category). It covers both when to use it and when to route elsewhere.

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