kupid_lms_announcements

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

With no annotations, the description carries the full burden. It discloses the return format (full HTML without truncation) and the conditional querying behavior based on course_id, providing transparency beyond the schema.

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, starting with the purpose, then explaining parameter behavior, and ending with an Args section. While efficient, the Args section partly repeats information already stated.

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?

For a simple tool with one optional parameter, the description covers essential aspects: return format, filtering behavior, and differentiation from a sibling. The output schema likely handles return structure details, so the description is adequately complete.

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 explain the parameter. It clearly states course_id is optional, what happens when omitted (all active courses), and references kupid_lms_courses for obtaining course IDs, fully compensating for the schema gap.

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 explicitly states the tool retrieves Canvas LMS announcements (Canvas LMS 공지(announcement)를 조회합니다). It contrasts with kupid_lms_dashboard by noting it returns full HTML without truncation, distinguishing it from a sibling tool.

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 explains the effect of providing or omitting the course_id parameter (specific course vs. all active courses) and references kupid_lms_courses for finding course IDs. However, it does not explicitly state when to choose this tool over other related siblings beyond the dashboard comparison.

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