clickup_template_apply_task

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

With no annotations provided, the description carries the full burden. It discloses that the tool creates a new task (mutation behavior) and returns the created task object (output behavior). However, it doesn't mention permission requirements, rate limits, error conditions, or whether the operation is idempotent—leaving gaps for a mutation tool.

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 the core action and inheritance, second provides prerequisite guidance, third specifies the return value. Each sentence earns its place, and the description is appropriately front-loaded with the main 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?

For a mutation tool with no annotations and no output schema, the description adequately covers the purpose, parameters (via schema), and basic behavior. However, it lacks details on error handling, authentication requirements, and the structure of the returned task object—leaving the agent with incomplete operational context.

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 the schema already fully documents all three parameters. The description adds marginal value by explaining that the name 'overrides the template's default name' (implied in schema) and that templates are discovered via 'clickup_template_list' (helpful context). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create a new task in a list by instantiating a saved task template') and distinguishes it from siblings like 'clickup_task_create' (which creates from scratch) and 'clickup_template_apply_folder/list' (which apply templates to different resources). It explicitly mentions inheritance of template properties like description, checklists, subtasks, and custom fields.

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 provides clear context for when to use this tool ('by instantiating a saved task template') and references 'clickup_template_list' as a prerequisite for discovering templates. However, it doesn't explicitly state when NOT to use it (e.g., vs. 'clickup_task_create' for creating tasks without templates) or mention alternatives among siblings.

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