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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully adds the pagination size (50 per page) and the underlying endpoint (GET /v2/users/{id}/courses), which is helpful operational context. Still missing: whether it requires auth/permissions, how results are ordered, and how to detect the last page.

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, tightly packed sentence front-loads the returned resource and adds dates, pagination size, and endpoint with no filler. It could be split for readability, but nothing is wasted.

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 read-only list tool with a fully documented schema, the description is adequate but not complete. It leaves out return ordering, how pagination terminates, and any relation to the sibling progress tool, though the output schema absence means it needn't explain return values in depth.

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 both 'page' and 'user' (id or email) are already documented. The description adds nothing specific about parameter syntax or semantics beyond what the schema provides, 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 (list), resource (courses), and scope (a user's enrollments) with the added detail of what fields are returned (enrollment and expiry dates). It's clear what the tool does, though it doesn't explicitly differentiate from the adjacent sibling learnworlds_get_user_course_progress.

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 implied by the description ('the courses a user is enrolled in'), giving natural context for when to reach for this tool. However, it offers no explicit when-to-use guidance, no exclusions, and no mention of alternatives like learnworlds_get_user_course_progress or learnworlds_list_course_users.

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