get_users_per_course

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

The description adds significant behavioral details beyond annotations: sorted order (most recent first), pagination, and default limit of 20 users per page. Annotations already indicate readOnlyHint=true, destructiveHint=false, so no contradiction. Additional context about pagination and ordering is valuable.

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 description is concise (4 lines) with clear structure: an emoji+HTTP header, a one-line summary, and a detailed sentence. It front-loads key info (read-only, course scope) and avoids unnecessary fluff. Every sentence serves a purpose.

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?

Given no output schema, the description explains sorting and pagination but does not describe the user object fields returned. For a read-only list tool with annotations (readOnlyHint, openWorldHint, idempotentHint), this is adequate but could be improved by mentioning common fields (e.g., id, name, email).

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 covers all 3 parameters with descriptions (100% coverage), so baseline is 3. The description adds value by explaining the default page size (20) and pagination behavior, which is not in the schema (items_per_page has no default). This enhances understanding of the list's structure.

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 clearly states it retrieves all users enrolled in a course specified by course id. It uses specific verbs ('Retrieves all users') and resource ('course'), and distinguishes from sibling tools like get_users (which gets all users without course filter) and get_users_community_space (different resource).

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?

The description implies usage for course-specific user enumeration with 'Get all users per course', providing clear context. However, it does not explicitly state when not to use it or mention alternative tools like get_users for non-course users. The sibling tools list offers contrast but no direct guidance.

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