Cheapest courses

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

Adds substantial behavior beyond the readOnly/idempotent annotations: the site cannot sort by price, so it scans the first 300 results (relevance-ordered for queries, popularity otherwise) and sorts locally. It also explains that `scanned` of `total` signals answer completeness — critical to interpreting a truncated result set.

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 purpose, then the caveat, then the next-step pointer — a good information order. Slightly verbose with the awkward line breaks and parenthetical asides, but every sentence carries 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?

For a 7-parameter, no-output-schema tool, the description covers result interpretation (scanned/total) and the caps on search coverage, which is what an agent most needs. Pagination behavior and the exact result fields beyond price are left implicit, so not fully complete.

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 coverage is 100%, so baseline would be 3, but the description adds genuinely new semantics: when `query` is set, category and type/level are silently ignored, which the schema alone does not convey. Price/limit semantics remain schema-only.

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 resource and ordering: 'Cheapest paid courses for a topic or category, ascending by final_price (what the customer pays).' This clearly separates it from siblings like mkh_free_courses and mkh_deals, and the trailing 'Next: mkh_course' hints at the follow-up tool.

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 concrete usage context: 'With query, category and type/level are ignored' tells the agent how parameters interact, and 'Next: mkh_course' suggests a chained call. It does not explicitly contrast with mkh_deals or mkh_free_courses, though the 'paid' scoping implies the boundary.

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