get_courses

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

With no annotations provided, the description carries the full burden. It discloses that this is a read-only listing operation scoped to 'active' and 'enrolled' courses, which is useful. However, it does not mention pagination, ordering, or how the optional account parameter affects results—though the output schema likely covers return shape.

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?

A single sentence that front-loads the verb and resource, with no filler or repetition. Every word contributes meaning, making it easy to parse quickly.

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?

The description is adequate for a simple list operation, and the output schema presumably documents the return payload. However, it leaves the 'account' parameter unexplained and offers no guidance on when this tool is preferable to or distinct from the many sibling tools, so some context is missing.

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 schema has one parameter, 'account', with a default of 'uchile' and no description. The tool description does not mention or explain this parameter at all, and schema description coverage is 0%. Since the description must compensate for undocumented parameters, its failure to address 'account' leaves the agent guessing about its meaning and allowed values.

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 uses a specific verb ('List') and resource ('all active enrolled courses from Canvas LMS'), clearly distinguishing it from sibling tools that operate on specific course content like assignments, announcements, or files. This leaves no ambiguity about what the tool returns.

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 implies this is the tool to call when you need the list of courses a user is actively enrolled in, which is a natural precursor to course-specific tools. However, it provides no explicit when-to-use guidance, exclusions, or contrast with siblings like get_assignments or get_course_pages.

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