skool_lessons_list

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

No annotations are provided, so the description carries the full burden. It only mentions an implementation detail ('Uses the Next.js classroom data route') and does not disclose read-only behavior, pagination, error conditions, or prerequisites. The agent cannot anticipate behavior beyond the basic listing semantics.

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 a single sentence, front-loaded with the core purpose and free of redundant filler. The second clause about the Next.js route is somewhat extraneous but does not bloat the text.

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 simple list operation with two well-documented parameters, the description is minimally adequate. However, with no output schema and no annotations, it does not explain response format, error handling, or how courseSlug is obtained in context, leaving some gaps for an agent.

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 schema already documents both parameters adequately. The description merely references 'course parameter,' which adds no meaning beyond the schema and uses slightly different terminology than courseSlug.

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 states a clear action and resource: 'List lessons/modules in a specific course.' This distinguishes it from course-level and post-level tools, though it does not explicitly name any sibling tool for contrast.

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 description gives no explicit when-to-use guidance, exclusions, or references to alternatives like skool_courses_list or skool_posts_list. The usage context is only implied by the purpose statement; adding a sentence about when to choose this over related tools would help.

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