Retrieve your enrolled Brightspace courses with their course IDs, optionally filtering to active courses only, so you can identify courses for deadlines, assignments, and grades.
List the student's own Brightspace course enrollments with their course IDs. Purdue Sensitive data.
| Name | Required | Description | Default |
|---|---|---|---|
| active_only | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description contributes one piece of non-structured context, the "Purdue Sensitive data" sensitivity marker, but omits meaningful behavior: that active_only defaults to true, meaning inactive enrollments are silently excluded.
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 the scope and return payload front-loaded; no padding. The trailing "Purdue Sensitive data" fragment is terse but carries real information, so nothing penalizes structure.
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?
An output schema exists, so return values need not be described. However, with an undocumented boolean parameter and no indication of how course IDs relate to downstream sibling tools, an agent lacks the context to call it with intent rather than by default.
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% for the single parameter, so the description carries the full burden and says nothing about active_only. It neither explains that the default of true hides inactive courses nor what false would return, leaving the only behavioral knob undocumented.
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 ... Brightspace course enrollments") and names the exact return content (course IDs), with a clear scope ("student's own"). It separates itself from siblings like list_assignments or get_course_outline by being the enrollment-level listing, though it never names those alternatives.
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?
Usage is only implied: an agent can infer this is the place to get course IDs before calling per-course tools. There is no explicit when-to-use, no exclusion against get_course_outline, and no note on when active_only should be toggled.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.