List course folders

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, covering safety. The description adds the navigational purpose but does not disclose details like pagination, ordering, or whether nested folders are returned. With annotations carrying the safety profile, this is adequate but minimal.

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?

One short sentence, front-loaded with the primary action and purpose. No wasted words; every element 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 read-only tool with one parameter and no output schema, the description is sufficient. It gives the purpose and the only parameter is already documented. A minor gap is that it doesn't specify whether the result includes only top-level folders or all nested folders, but this is not critical for a listing operation.

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 describes courseId as 'Canvas course id' with 100% coverage. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate. The tool has only one parameter, so there is little to compensate for.

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 states a specific verb+resource: 'List a course's folders'. It is distinct from siblings like canvas_list_course_files (files vs folders) and canvas_get_file. The parenthetical 'for navigating the file tree' further clarifies its role, making it easy to differentiate.

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 gives clear context: 'for navigating the file tree' implies when to use it. It does not explicitly name alternatives or exclusions, but the sibling landscape makes it obvious that this is for folders, not files or other resources. It lacks an explicit 'use X instead when...' but the intent is clear.

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