clickup_folder_delete

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

No annotations are provided, so the description carries full burden. It thoroughly discloses behavioral traits: destructive, irreversible, cascading (deletes all descendants), requires user confirmation, and returns empty object on success. This covers safety, permanence, scope, and output behavior.

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?

Three sentences with zero waste: first states purpose and severity, second provides usage guidance and alternative, third describes return value. Each sentence earns its place by adding critical information.

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 destructive tool with no annotations and no output schema, the description provides complete context: purpose, behavioral warnings, usage guidelines, parameter context, and return value. It compensates fully for the lack of structured metadata.

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 baseline is 3. The description adds value by reinforcing the cascading effect ('All descendant lists and tasks are deleted with it') and mentioning clickup_folder_list as the source for folder_id, which provides practical guidance beyond the schema's technical definition.

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 clearly states the specific action ('permanently delete'), target resource ('ClickUp folder'), and scope ('along with every list and task inside it'). It distinguishes from sibling tools like clickup_space_update for archival and clickup_folder_list for obtaining IDs.

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?

Explicitly states when to use ('permanently delete') and when not to use ('If you only want to hide the folder, use clickup_space_update with archived=true instead'). Provides clear alternative and prerequisite (confirm with user before calling).

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