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

Annotations already declare this a safe, idempotent read, so the bar is lower, and the description still contributes real behavior: results are pseudonymized ('Members appear under pseudonyms') and access is limited to lecturers. It stops short of describing ordering, pagination, or how to resolve pseudonyms back to identities.

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?

Two short sentences, front-loaded with the operation and followed by the two facts an agent cannot get from structured fields: the pseudonymization and the lecturer restriction. Nothing is redundant.

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 one-parameter read tool with rich annotations and no output schema, the description covers what is returned (role, status), who may call it, and the privacy caveat. The main residual gap is the unresolved ambiguity of 'for its Lecturers only' and the absence of any note on result size or paging.

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 a single required parameter at 100% schema description coverage, and the schema already explains that courseId comes from list_courses. The description adds no format or sourcing detail beyond the schema, so the baseline 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?

The description names a specific verb and resource ('Lists a Course's Members') and adds the returned fields ('with role and status'), so the operation is unambiguous. It does not differentiate itself from any named sibling, and 'for its Lecturers only' is slightly ambiguous between an access restriction and a result filter.

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: the reader infers this is the way to enumerate a course's membership, presumably after obtaining an id from list_courses. There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named, though the 'Lecturers only' clause hints at a caller prerequisite.

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