Current deals

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description adds non-obvious behavior beyond that: the result ordering (biggest discount first) and the meaning of the ends_in_seconds field. It does not discuss pagination or the limit's interaction with total result count, so it stops short of full coverage.

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-loaded with the core purpose and efficient overall. The sentence explaining ends_in_seconds is slightly orphaned since that field does not appear in the input schema, adding minor noise to an otherwise tight description.

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?

Purpose, usage, and ordering are complete, and an output schema exists so return values need not be enumerated. The only mild gap is that pagination/result-count behavior is unstated, which matters for a listing tool with a capped limit.

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?

Only one parameter (limit) and schema description coverage is 100%, so the schema fully documents it. The description adds no syntax, bounds, or default information beyond what the schema already provides; 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?

Specific verb + resource + scope ('List every product on MasterKala's discount page right now') plus an ordering guarantee ('biggest discount first'). It also explicitly separates itself from mk_search and mk_browse, which cover keyword/category discounts.

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?

States the triggering intents ('what's on sale' / 'best discounts today') and names the alternatives for a different scope (keyword or category discounts → mk_search / mk_browse). Both when-to-use and when-to-use-something-else are present.

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