list_folders

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the scope ('in a course') and adds no detail about return format, pagination, ordering, or whether only top-level folders are returned. It offers little beyond what the tool name already implies.

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 five-word sentence with no filler, and the core action and scope are front-loaded. It is appropriately sized for the simplicity of the operation.

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 one-parameter list operation this description is minimally viable, but the absence of annotations, output schema, and any note about folder hierarchy or pagination leaves some context gaps. The abundance of sibling list tools also makes a bit more contextual guidance valuable.

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 already documents course_id with a description, so schema coverage is 100%. The tool description adds no additional meaning for the parameter, but it does not need to compensate for any schema gap.

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') with a clear scope ('in a course'), making the operation unambiguous. It distinguishes from sibling tools like list_files or list_courses without requiring schema inspection.

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 phrase 'in a course' implies the tool is for retrieving folders within a specific course context, but no explicit when-to-use or when-not-to-use guidance is given. It does not mention alternatives or conditions for choosing a different list tool.

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