canva_list_folder

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

No annotations are provided, so the description carries the full burden. It implies a read-only listing but discloses nothing about pagination, ordering, permission requirements, or whether the call is recursive versus single-level.

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 sentence with no filler, and the key scoping hint ('root') is placed where it is immediately visible. Nothing is wasted.

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?

The tool is simple (one optional parameter, no output schema), and the description covers the core invocation. It still omits what the returned items look like and whether traversal is recursive, which matters for an agent deciding between this and canva_list_designs.

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 0% and the single folder_id parameter has no description in the schema. The description compensates partially by explaining the 'root' default value, but it does not clarify whether a folder ID is accepted in another form or what happens for invalid IDs.

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?

States a specific verb (List) and resource (items in a Canva folder), which is clear on its own. It does not, however, distinguish itself from sibling listing tools like canva_list_designs, so an agent must infer the scope difference.

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 parenthetical '(root for the top level)' implies the intended entry point for folder traversal, giving implicit usage guidance. There is no explicit when-to-use vs when-not-to-use statement or mention of alternative listing tools.

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