kupid_lms_courses

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

With no annotations, the description must disclose behavioral traits. It only states that SSO login is required, which is a prerequisite, but does not mention whether the operation is read-only, any side effects, or data returned beyond 'list of courses'. The output schema exists but is not described.

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 short with three sentences, front-loading the purpose. However, the second sentence ('It brings the list...') is somewhat redundant with the first. Overall clear and efficient.

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 zero parameters and an existing output schema, the description is adequate but lacks details on what fields the returned list contains, any ordering, or pagination. It does not distinguish from similar sibling tools like kupid_my_courses, making it less complete for an agent.

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 tool has zero parameters, so schema coverage is 100%. The description adds no parameter-specific information, which is acceptable as no parameters exist. Baseline score of 4 applies.

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 a list of enrolled courses from Canvas LMS, specifying the source URL. The purpose is clear, but it does not explicitly differentiate from sibling tools like kupid_my_courses or kupid_search_courses.

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 mentions the need for SSO login but provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The 'kupid' prefix suggests integration with a specific portal, but usage context is lacking.

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