Show Course Enrollments

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds one useful behavioral fact — only 'active' enrollments are returned — but says nothing about pagination, result volume, or how progress data is shaped.

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 front-loaded sentence with no filler or redundancy. It is efficient, though so terse that it omits information an agent would benefit from.

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 a 5-parameter schema fully documented and annotations covering the safety profile, the description is close to sufficient. But it omits return-shape/pagination expectations and leaves the 'student progress' claim unclarified relative to get_course_progress, so it is only minimally adequate.

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 coverage is 100%, so every parameter (including sort_direction, enrolled_in_after/before, and account) is documented in the schema itself. The description only restates that a course is required, adding no syntax or filtering nuance beyond the schema.

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?

Names a specific verb ('Fetch'), resource ('active enrolled students'), and scope ('for a specific course'), so the operation is understandable at a glance. It does not differentiate itself from siblings like get_course_progress or list_users, and the phrase 'and student progress' is ambiguous since a separate get_course_progress tool exists.

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 when-to-use guidance is given. The description never mentions alternatives such as create_enrollment, unenroll_user, or get_course_progress, nor the condition that should pick this tool over them. Context is implied only by the name.

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