kupid_lms_syllabus

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

The description discloses that the tool automatically resolves course_code to course_id using the course list, which is a helpful behavioral trait. However, with no annotations provided, it does not mention error handling, authentication requirements, rate limits, or any side effects beyond a pure read operation.

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 concise and well-structured with an 'Args' section, though it includes both Korean and English which may be slightly redundant. It uses bullet-like formatting for parameters, making it easy to parse.

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?

Given the existence of an output schema (not shown), the description adequately covers the tool's functionality. It could be improved by addressing the similarity to 'kupid_get_syllabus' or clarifying the priority when both parameters are provided.

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?

The description adds significant meaning beyond the schema: it explains that course_code is a course code like 'BDC115', that course_id comes from 'kupid_lms_courses', and that either parameter can be used. This compensates for the 0% schema description coverage well.

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 states it retrieves the syllabus for a course, using the verb '조회합니다' (retrieve). However, there is a sibling 'kupid_get_syllabus' with a similar purpose, and the description does not differentiate itself from that tool, which could confuse an AI agent.

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 description provides usage instructions for the two parameters (course_code and course_id) and explains how they relate, but it does not specify when to use this tool over alternatives like 'kupid_get_syllabus' or if there are any prerequisites (e.g., needing to call 'kupid_lms_courses' first to get course_id).

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