clickup_template_apply_task

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

Describes inheritance of description, checklists, subtasks, etc., and mentions that the new task uses the supplied name. States return value. Without annotations, this provides solid behavioral insight, though permission requirements and side effects are omitted.

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 compact sentences: first defines action and key behavior, second offers usage guidance and return info. No wasted words, front-loaded with core purpose.

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?

Given 3 params, full schema coverage, and no output schema, the description covers purpose, inheritance, parameter sources, and return type. Complete enough for correct tool selection and invocation.

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 has 100% coverage, and the description adds extra meaning: source of list_id and template_id from other tools, and name override behavior. This significantly helps parameter usage.

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 clearly states the tool creates a new task by instantiating a task template, distinguishing it from related sibling tools like clickup_task_create and clickup_template_apply_folder.

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 mentions to use clickup_template_list for discovering templates, providing helpful context. Does not explicitly state when not to use, but the purpose is clear enough to infer.

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