canva_list_folders

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does not explain pagination behavior despite the continuation parameter, does not state whether listing is recursive or limited to direct children, and gives no detail on how the itemType filter behaves or what the response looks like.

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 front-loaded sentence with the verb first and zero wasted words. It is efficiently structured, though slightly longer coverage of pagination or usage would have improved value without harming conciseness.

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?

With no annotations, no output schema, and only a terse one-line description, the tool is under-specified for an agent that must choose among nine siblings. Pagination semantics, the itemType filter's value domain, and the distinction from canva_list_folder_items are all 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter meaning beyond the schema, and while the schema documents both parameters, itemType's valid values remain unspecified in either source.

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 ('Lista' / lists) with a clear resource ('elementos y subcarpetas' / elements and subfolders) and a defined scope ('carpeta raíz' / root folder). However, the name (list_folders) slightly conflicts with the described behavior (listing elements AND subfolders), and it does not explicitly differentiate itself from the sibling canva_list_folder_items.

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?

No guidance is given on when to use this tool versus its siblings. With nine sibling tools including the near-identical canva_list_folder_items and canva_list_designs, the absence of any routing guidance or exclusions leaves selection to inference.

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