kupid_lms_assignments

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

No annotations are provided, so the description must disclose behavioral traits. It implies a read operation ('조회합니다' means inquiry) but does not explicitly state it is non-destructive or mention other behaviors like pagination, rate limits, or authentication requirements. This is adequate but minimal.

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 very concise with no fluff. It front-loads the main purpose in a single sentence, followed by a brief body and clearly formatted parameter descriptions. Every sentence adds value.

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 presence of an output schema (return values are covered), the description provides sufficient context for an agent: purpose, prerequisite, parameter semantics, and default behavior. It lacks details on error handling or ordering, but these are minor for a list 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?

With 0% schema coverage, the description adds meaningful explanations for both parameters: course_id is the ID from kupid_lms_courses, and upcoming_only filters with a default value. This goes beyond the schema's bare titles and types, providing clear guidance.

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?

Description clearly states the tool retrieves Canvas LMS assignments for a specific course, using specific verbs and distinguishing from sibling tools like kupid_lms_quizzes and kupid_lms_grades. It also explains default behavior (returns all assignments).

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?

Description explicitly instructs users to first check course_id using kupid_lms_courses (a prerequisite) and explains the effect of the upcoming_only parameter. However, it does not mention when not to use this tool versus alternatives like kupid_lms_submissions.

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