clickup_folder_list

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

No annotations are present, so the description carries full burden. It states the return format as 'a compact array of folder objects (id, name, task_count, archived)', which is transparent for a read operation. It does not explicitly confirm read-only behavior, but the context implies it. The description could mention that no side effects occur, but the provided details are adequate.

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?

Two sentences cover purpose, context, alternative, and return format. No unnecessary words. The description is front-loaded with the primary action and uses the second sentence for differentiation. Extremely concise and structured.

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 two parameters, full schema coverage, no output schema, and a simple list operation, the description provides sufficient context. It covers what the tool does, when to use alternatives, how to get required IDs, and what the output looks like. Nothing essential is 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 coverage is 100%; both parameters are already well-described in the schema. The description adds value by telling the user to obtain space_id from clickup_space_list, which goes beyond the schema. This extra guidance improves parameter semantics.

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?

Description starts with 'List all folders in a ClickUp space', clearly stating the action and resource. It distinguishes from clickup_list_list by noting that spaces may have folderless lists and directing users to that tool for those. This differentiates it from a sibling tool.

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 explicitly says 'Folders are optional groupings that contain lists; a space may also have folderless lists (use clickup_list_list with space_id for those).' This tells when to use this tool and when to use the alternative, providing clear context and conditions.

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