List Course Folders

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

With no annotations, the description carries the full burden of behavioral disclosure. It signals a read-only listing operation and the course scope, but it does not mention whether folders are top-level only or recursive, nor pagination behavior, which are relevant for a folders API.

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, front-loaded sentence with no filler or redundant phrasing. Every word contributes to identifying the action, target, and scope.

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?

This is a low-complexity tool with one fully documented parameter, so the description is mostly sufficient for correct invocation. The main gap is that there is no output schema and no statement about whether the returned folders are nested or flat, but the simplicity of the tool keeps this from being a major deficiency.

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 100%, and course_id is already clearly documented in the input schema as the Canvas course ID. The tool description adds no additional parameter-specific nuance, but the baseline score of 3 is appropriate because the schema already provides complete parameter meaning.

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 ('folders') scoped to a single Canvas course, making it easy for an agent to distinguish this from sibling tools like list_course_files, list_course_modules, or list_course_assignments. It clearly answers what the tool does.

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 intended usage is implied by the name and description: call this when you need folders within one course. However, it does not explicitly state when to prefer this over alternatives or provide exclusion criteria, leaving the choice somewhat to inference.

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