clickup_template_apply_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 details what the new folder inherits (list structure, statuses, default fields, presets) and that it returns the created folder object. It does not mention error conditions or side effects, but the core behavior is transparent.

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 three sentences, concise and front-loaded with the main action. Every sentence provides necessary information without redundancy.

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 tool with 3 parameters and no output schema, the description adequately covers the functionality. It explains the template inheritance and return value. Minor gaps include lack of error handling or prerequisites beyond template discovery, but overall sufficient.

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 input schema covers 100% of parameters with descriptions. The description adds value by noting that space_id and template_id are obtained from other tools (clickup_space_list, clickup_template_list) and reinforces the uniqueness requirement for name, beyond the schema.

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 action: 'Create a new folder in a space by instantiating a saved folder template.' It specifies the resource (folder) and distinguishes it from sibling template application tools (like clickup_template_apply_list for lists and clickup_template_apply_task for tasks).

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 explains the usage context: it is for creating a folder from a template, and mentions using clickup_template_list to discover templates. It implicitly differentiates from clickup_folder_create (which creates a blank folder) by focusing on template instantiation, though it does not explicitly state when not to use it.

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