skool_courses_list

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

With no annotations provided, the description must carry the behavioral disclosure burden. It conveys that this is a read-style listing operation and states what is returned, but it does not mention authentication needs, pagination, or how groupId vs community impacts behavior beyond what the schema already states.

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 short sentences with no wasted words. The action is front-loaded, and the return-value sentence earns its place by giving the agent a preview of what the call produces.

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 two-parameter list tool, the description plus schema is mostly workable, but it is not fully complete: there is no output schema, no explicit read-only confirmation, and no guidance for choosing between this and the lessons/posts siblings. The description covers the basics but leaves several selection and behavior questions open.

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 groupId and community clearly, including the api2.skool.com behavior and default config fallback. The description adds no parameter-level meaning beyond saying 'community classroom,' so the baseline of 3 is appropriate.

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 states the action ('List courses'), the resource ('in a community classroom'), and the return payload ('course names and metadata'). It differentiates from siblings like skool_lessons_list and skool_posts_list by naming the course resource, though it does not explicitly contrast itself with a sibling.

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 guidance on when to choose this tool over alternatives such as skool_lessons_list, nor does it mention prerequisites or the difference between listing courses vs lessons. Usage context is only implied by the verb and resource.

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