list_enrolled_users

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

With no annotations, the description must carry the full burden of disclosing behavioral traits. It only mentions the return format (which is likely covered by the output schema) and does not disclose whether the operation requires specific permissions, how errors are handled, or any rate-limit implications. The non-destructive nature is implied but not stated.

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 crisp, well-organized, and front-loaded with a one-sentence summary. It then breaks down arguments and return values in a structured way without excess verbiage.

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 operation, the description covers the essential invocation details: what it lists, what parameters mean, and what the output shape is. It lacks usage guidance and permission context, but given the simple nature and presence of an output schema, it is sufficiently complete for correct invocation.

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 0%, but the description fully compensates by explaining course_id as 'The Moodle course ID' and role with examples and default behavior ('Empty = all'). It adds practical meaning beyond the raw schema, including a list of common role values.

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 'List users enrolled in a course with their roles', using a specific verb and resource. It distinguishes the tool from siblings like list_group_members (group-specific) and get_grades_report (grade-specific) by focusing on enrolled users and role information.

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?

No guidance is provided on when to use this tool versus alternatives such as list_group_members or get_course_grades. The description only states what it does, not under what circumstances it should be chosen, and lacks any exclusions or context about alternative tools.

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