skool_courses_list

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

With no annotations provided, the description carries the full burden. It clearly states the action ('List') which implies a read-only operation, and adds that it returns 'course names and metadata,' providing basic behavioral transparency. It does not mention side effects, auth, or rate limits, but for a list operation the core safety profile is evident.

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 two short sentences with no filler words. Every word earns its place, front-loading the action and resource, then adding the return type. It is appropriately sized for the tool's simplicity.

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?

No output schema exists, so the description's mention of 'course names and metadata' is helpful but still minimal. It does not explain the distinction between 'groupId' and 'community', nor any pagination or filtering behavior. For a simple list tool, this is adequate but leaves clear gaps in the agent's understanding of richer data via groupId.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond what the schema already provides for 'groupId' and 'community', so it does not exceed the baseline.

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 uses a specific verb ('List') and resource ('courses in a community classroom'), making the tool's purpose clear. It also distinguishes from sibling tools like 'skool_lessons_list' by specifying 'courses' rather than 'lessons'.

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 implies usage for listing courses in a classroom, but it does not provide explicit when-to-use guidance or contrast with alternatives such as skool_lessons_list or skool_posts_list. It is minimally viable but lacks clearer context for tool selection.

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