kupid_lms_grades

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

With no annotations provided, the description carries the full burden. It indicates a read-only lookup ('조회') but does not disclose details about side effects, permissions, rate limits, or output format. The presence of an output schema mitigates some need, but the description could add more behavioral context.

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 without any wasted words, presented in both Korean and English with clear structure. Essential information is front-loaded, and every sentence contributes to understanding.

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 simple single-parameter input and the existence of an output schema, the description adequately covers purpose, prerequisite, and outputs. It does not discuss error handling or edge cases, but for a lookup tool, this is sufficient.

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. It explains the course_id parameter meaning and directs to kupid_lms_courses.id for obtaining it, adding significant value beyond the schema's minimal 'Course Id' title.

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 the tool retrieves grades/scores from Canvas LMS for a specific course, listing specific outputs (current score, final score, grade). It references the prerequisite tool kupid_lms_courses, distinguishing it from siblings like kupid_get_all_grades.

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 explicitly instructs to first check the course_id using kupid_lms_courses, providing clear context for when to use this tool. However, it does not mention when not to use it or alternative tools such as kupid_get_all_grades.

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