Retrieve a single overview of enrolled courses, pending assignment deadlines, and incomplete online lectures at Kwangwoon University to quickly assess your academic status.
광운대 KLAS 수강 과목, 마감 임박 과제, 미수강 온라인 강의 종합 현황을 한 번에 요약 조회합니다.
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | ||
| deadline_days | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It conveys read-only intent through '조회', but it does not disclose that the KLAS session must be authenticated, what happens without one, or any limitation on freshness of the overview data. These are important for safe invocation.
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, concise sentence that identifies the tool's scope without fluff. It could be slightly improved by front-loading the exact subject covered, but the current structure is adequate and economic.
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 tool aggregates multiple domain concerns but the description does not explain how parameters shape the result, whether authentication is required, or what distinguishes it from the sibling functions in practical selection. The output schema helps with return values, but the context around invocation is incomplete.
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%, and the description does not explain either parameter. 'term' is left to the reader to interpret (semester code, academic year, or empty default), and 'deadline_days' is never connected to the mentioned '마감 임박' threshold.
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 clear query verb (조회합니다) and names the exact scope: KLAS courses, imminent assignments, and unwatched lectures. By calling it a comprehensive summary, it clearly distinguishes the tool from narrower siblings such as klas_list_courses, klas_get_deadlines, and klas_get_lecture_progress.
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?
The phrase '종합 현황을 한 번에' implies this tool is for a broad dashboard-style overview rather than detailed lists. However, it never explicitly says when to prefer this over a sibling, and it provides no exclusion criteria or conditions for when a more specific tool should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.