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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value beyond them by disclosing the sort order ('newest first') and the returned attributes (title, products, group managers, capacity, tags). It does not mention pagination behavior despite the page parameter, which is the main residual gap.

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?

A single front-loaded sentence covering purpose, scope, sort order, returned fields, and the underlying endpoint, with no wasted words.

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 read-only list tool with no output schema, the description covers what is returned and in what order, which is what an agent needs. The only omission is pagination guidance for the page parameter, which is minor here.

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?

There is one parameter (page) with 100% schema description coverage, so the schema already explains its semantics. The description adds nothing about paging limits or defaults, so it neither compensates nor detracts - baseline 3.

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 (List) and resource (the school's user groups), and clarifies the domain jargon with '(cohorts / B2B seats)' plus the API endpoint GET /v2/user_groups. This clearly separates it from siblings like learnworlds_list_users and learnworlds_list_course_users.

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?

Usage is only implied by the verb - an agent can infer this is the way to enumerate groups, but the description never states when to prefer it over learnworlds_list_users or learnworlds_list_course_users, nor any prerequisites. No explicit when/when-not guidance is given.

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