Lists accessible Brightspace course enrollments with pagination, helping assistants identify a student's active courses and continue fetching results when more are available.
List accessible course enrollments, respecting activeOnly and includeCourseIds. Check sourceComplete and nextOffset.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size; defaults to 50. | |
| offset | No | Result offset; defaults to 0. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful pagination behavior by telling the agent to check 'sourceComplete' and 'nextOffset'. However, it never explains what those fields mean or what happens when sourceComplete is false, and it names two flags that are not in the schema.
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 with no filler, and the core purpose is front-loaded. The second sentence is cryptic shorthand ('Check sourceComplete and nextOffset') that does not earn its place without explaining what to do with those values.
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?
There is no output schema, so the description carries the burden of explaining return values. It gestures at sourceComplete and nextOffset but never defines them, and it omits what a course enrollment contains. The stray parameter names also create real ambiguity about how to call the tool.
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 limit and offset are already documented with defaults and bounds. The description adds nothing about those two parameters and instead references 'activeOnly' and 'includeCourseIds', which do not exist in the schema, risking an agent attempting to pass unsupported arguments.
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?
States a specific verb and resource: 'List accessible course enrollments'. That is clearly distinguishable from the get_* siblings, which fetch single resource types. The second clause muddies it by citing 'activeOnly and includeCourseIds', which are not parameters of this tool.
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 when-to-use or when-not-to-use guidance and no reference to alternatives such as brightspace_search_course or brightspace_check_updates. An agent must infer that this is the enumeration entry point for a user's courses.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.