Discounted courses

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

Beyond annotations, the description discloses important behavior: it scans the 300 most popular paid courses of the category and filters from there, sales are time-limited, and discount end dates must be retrieved via mkh_course. This adds meaningful operational context that the annotations do not provide.

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?

The description is short and front-loads the core result: discounted courses sorted by discount. The return fields and follow-up tool are packed efficiently, though the terse 'Next: mkh_course.' ending is slightly abrupt.

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?

For a read-only list tool with fully described input parameters, the description covers scope, sorting, key return fields, and the time-limited nature of sales. It does not fully explain pagination or response shape, but no output schema exists and the core behavior is adequately described.

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 the parameters are already well documented with defaults, bounds, and examples. The description reinforces category scope and filtering behavior, but it does not add parameter-specific semantics beyond what the schema already states.

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?

The description clearly identifies the resource as currently discounted courses, states the sort order as biggest discount first, and names the returned discount/price fields. It distinguishes this from free or cheapest-course siblings by focusing on active discounts, though it does not explicitly contrast alternatives beyond pointing onward to mkh_course.

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?

Usage is implied by the title and description: the tool is for finding courses that are currently discounted. It gives an explicit next step ('Next: mkh_course') for discount end dates, but does not say when to prefer this over siblings such as mkh_cheapest or mkh_search, nor does it state exclusions.

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