List Folders

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

With readOnlyHint: true and openWorldHint: true annotations present, the bar is lowered. The description is consistent with these annotations (listing is read-only) and adds a small behavioral detail: it returns 'all' folders in the course rather than a filtered subset. It doesn't contradict the annotations, but it also doesn't disclose pagination, recursion, or ordering behavior.

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?

Six words, front-loaded with the action, zero wasted verbiage. Every word earns its place.

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, single-parameter list operation with readOnlyHint and openWorldHint annotations, this is nearly complete. A bit more context on whether nested/child folders are included would push it to a 5, but the simple surface area makes the current description adequate.

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 coverage is 100% (course_id: 'The Canvas course ID'), and the description adds no parameter-level detail. This is the baseline 3 where the schema does the heavy lifting; the description doesn't need to compensate.

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?

'List all folders in a course' uses a specific verb (List), a clear resource (folders), and explicit scope (all in a course). It's unambiguous and distinguishes from the sibling `list_files` by resource type, though it doesn't explicitly contrast naming concerns.

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?

There is no explicit guidance on when to use this tool vs. alternatives or when not to use it. The usage is implied by the name and phrasing, but no exclusions, prerequisites, or alternative recommendations are provided.

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