list_lessonsList a course's lessons with teacher, progress, video paragraphs, and PDF handout status; include objectives and media URLs when compact=false.
List the lessons of a course with teacher, progress, video paragraphs and whether a PDF handout exists. Set compact=false for objectives and media URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| course | Yes | Course code from list_courses, e.g. 0662509SECSS01 | |
| compact | No | Omit objectives and URLs |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond that by disclosing what the response contains (teacher, progress, video paragraphs, PDF handout presence) and how the compact flag changes the payload — important since there is no output schema.
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?
Two sentences, zero filler, with the response-content summary front-loaded and the compact behavior stated second. Every clause earns its place.
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 usefully sketches the return shape and ties the course parameter back to list_courses. Minor gaps like pagination or ordering across lessons are not addressed, but nothing essential to invoking it correctly is missing.
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 both parameters are already documented. The description still adds actionable meaning by framing compact as an opt-in switch ("Set compact=false for objectives and media URLs"), telling the agent when flipping it is worthwhile rather than just what it does.
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 the lessons of a course") and enumerates the returned fields. It does not explicitly distinguish itself from the sibling get_lesson, though the singular/plural split is reasonably obvious.
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?
The usage guidance is only implied: listing lessons for a course is clearly the batch counterpart to get_lesson, and the course code reference to list_courses hints at a prerequisite. There is no explicit when-to-use or when-not-to-use statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.