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

Annotations declare readOnlyHint=true, so the safety profile is already covered and the description does not need to restate that. Instead it adds genuinely useful behavioral context: the exact set of returned metrics (progress rate, average score, time on course, completed units, per-section/per-activity breakdown), which is valuable because there is no output schema. It does not mention pagination, permissions, or error behavior, keeping it out of 5 territory.

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 compact sentence front-loads the core deliverable (progress in one course) and appends the raw API endpoint for precise mapping. There is no filler or repetition, though the endpoint reference is metadata rather than agent-facing guidance.

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?

With no output schema, the description steps in to enumerate the returned fields, which is exactly the gap it needed to fill for a two-parameter read tool. Combined with readOnlyHint covering safety, an agent has enough to call it correctly, though nothing is said about auth requirements or identifier fallback behavior.

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% — both 'user' (id or email) and 'course_id' (slug, e.g. "my-first-course") are fully documented in the schema, including that different identifier formats are accepted. The description adds no parameter-level detail beyond this, so the baseline of 3 is correct.

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 names the exact resource (a single user's progress in one course) and enumerates the payload it covers: status, progress rate, average score, time on course, completed units, and a per-section/per-activity breakdown. This is far more specific than a tautology and lets an agent distinguish it from aggregate tools like learnworlds_get_course_analytics or learnworlds_get_course_grades. It stops short of explicitly naming the sibling it is not, so a 5 is not warranted.

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?

There is no statement of when to use this tool versus alternatives such as learnworlds_get_course_grades, learnworlds_list_user_courses, or learnworlds_get_course_analytics. The endpoint mapping (GET /v2/users/{id}/courses/{cid}/progress) implies the single-user, single-course scope, but no exclusion or routing guidance is given. A reader must infer all usage conditions.

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