list_enrollments

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the tool's name and gives no information about read-only behavior, pagination, default enrollment types, response shape, or required permissions. The per_page parameter implies pagination, but the description does not confirm any behavioral details.

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 a single, efficient sentence with no redundant wording or filler. It is front-loaded and easy to parse. It is sparse, but for conciseness it earns a solid score.

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?

The description is too minimal to be contextually complete. With no annotations and no output schema, it does not clarify the return format, pagination behavior, or the difference from sibling tools like get_user_enrollments and list_students. The schema covers parameters, but the description leaves the agent without enough context for correct invocation and result interpretation.

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%, so all parameters are already documented with meaningful descriptions in the input schema. The description adds no additional parameter-level semantics beyond what the schema provides, matching the baseline expectation.

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 uses a specific verb and resource: 'List enrollments in a course.' It is clear and unambiguous about the core action, but it does not differentiate itself from sibling tools such as get_user_enrollments or list_course_users, so it falls short of a 5.

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 guidance on when to use this tool versus alternatives. The description does not mention that this tool is for course-scoped enrollment listings as opposed to user-scoped listings, nor does it provide any context for choosing it over list_students or list_course_users.

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