klas_get_lecture_progress

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It indicates a read-only query via '조회합니다' but says nothing about authentication needs, session freshness, empty-result behavior, or limitations. This is minimal disclosure for a query tool.

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 compact sentence that front-loads the object and then specifies the retrieved data. There is no filler, redundancy, or irrelevant detail, making it appropriately sized for a simple query tool.

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 the return shape is presumably covered. However, the description does not help an agent choose between this tool and klas_get_deadlines or klas_get_overview, and yearhakgi remains semantically unclear. For a simple query this is close to viable, but it still has meaningful gaps.

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 adds little for parameters. '특정 과목' loosely maps to course_id, but the required parameter is never named, and yearhakgi is not explained at all, including the meaning of its default empty string. Agents are left to infer semantics from parameter names alone.

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 states a clear operation ('조회합니다' / retrieves) and a specific resource: a specific course's online video lecture progress rate and attendance deadline schedule. It is clear about the data domain, though it does not explicitly differentiate itself from sibling tools like klas_get_deadlines or klas_get_overview.

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?

There is no guidance on when to use this tool versus alternatives such as klas_get_deadlines or klas_get_overview, and no mention of prerequisites like authentication or how to obtain a valid course_id. The phrase 'specific course' only implies that a course must already be selected.

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