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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond the annotations: the authentication requirement ('Needs the user's Cotlet API key with access to this app') and a description of the returned structure (modules in order, unlock rule 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 content is front-loaded with the core action, but the first and second sentences overlap heavily ('Courses in the Classroom with their modules...' vs 'Lists courses in the group's Classroom with their modules in order'), and the unlock-rule explanation is stated twice in near-identical terms, wasting space.

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 single-parameter list tool with no output schema, the description covers the return shape, the meaning of the unlock rule, auth requirements, and one usage scenario. Pagination or ordering/count limits are not addressed, but nothing critical for calling 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?

Only one parameter with 100% schema description coverage, so the schema already documents 'group' fully. The description's reference to 'the group's Classroom' reinforces context but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 ('Lists courses in the group's Classroom with their modules in order') and further specifies the returned attributes (modules, unlock rule, URL). This clearly distinguishes it from sibling skool tools like list_posts, list_members, or list_groups, which target different resources.

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?

Offers one concrete usage hint ('Use the module URLs in welcome messages'), which implies a context. However, it never says when to prefer this over alternatives or when it is not applicable, so usage remains largely inferred rather than explicit.

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