Get the full markdown of one lesson by slug. Teach from it: lead with the why, then run the exercise with the learner's real work.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Lesson slug from list_lessons / start_session. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states 'get' – a read operation – but omits any behavioral traits like idempotency, auth requirements, or side effects. Minimal disclosure.
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: first states core function, second provides usage guidance. No extraneous content, front-loaded.
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?
Given no output schema and simple single-param input, description covers purpose, usage, and parameter origin. Lacks details on markdown structure or limitations, but adequate for the tool's simplicity.
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% with slug description. Description adds meaningful context about slug's origin (from list_lessons/start_session), enhancing understanding beyond 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?
Clearly states it retrieves the full markdown of a lesson by slug, with a pedagogical usage hint. Distinguishes from siblings like list_lessons (listing) and complete_lesson (completing).
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?
Explicitly says to use with a slug from list_lessons/start_session, implying when to use. Could better exclude alternatives, but provides actionable context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: lesson management, session handling, admin operations, feedback, and overview. No two tools overlap in functionality.
Most tools follow a verb_noun pattern (e.g., complete_lesson, start_session), but 'overview' is a plain noun, breaking the pattern. The rest are consistent.
9 tools is well-scoped for a course management system, covering all essential operations without bloat.
Covers lesson lifecycle, session management, admin actions, and feedback. Minor gap: no tool for editing lesson content, but not core to the server's purpose.
