obs_get_elective_poolRetrieve all courses that can fill an elective slot in a student's course plan by providing the group ID.
Return every course that can fill one elective slot of the student's course plan, by group id.
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden. 'Return every course' conveys a read-only query with no destructive side effects, and 'by group id' indicates a simple parameterized lookup. However, it does not disclose authentication requirements, data freshness, or any filtering beyond the group id.
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 sentence with no filler. It front-loads the tool's core behavior and scopes it to the student's course plan, making every word meaningful.
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?
Although an output schema exists to explain return values, the description is incomplete for safe invocation: the single required group_id parameter is undefined, and there is no usage context to distinguish this from similar elective-related tools. The agent is left to guess how to obtain group_id and when to prefer this 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 description coverage is 0%, so the description must compensate for the bare group_id integer field. The description only says 'by group id' and does not explain what a group id is, where the agent obtains it, or how it relates to the elective pool. This leaves the required parameter under-specified.
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 names the operation ('Return every course') and the specific resource ('courses that can fill one elective slot of the student's course plan'). It is specific enough to identify the tool's function, but it does not distinguish itself from the similarly named sibling obs_get_elective_options.
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 provided, no alternatives are named, and no exclusions or prerequisites are mentioned. The description states what the tool does but not when an agent should select it over obs_get_elective_options or other listed course-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.