clickup_add_task_to_list

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds critical behavioral context: requires specific ClickApp, does not move the task, returns confirmation or error string, and details error handling for 403 and 404.

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 well-structured with clear sections (description, prerequisites, when to use/not use, returns, examples, error handling). Every sentence is informative and earns its place, with no 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?

Given the tool's complexity (requires a ClickApp, has a specific behavior distinct from move), the description covers all necessary aspects: prerequisite, use cases, alternatives, return format, and error handling. It is complete for an agent to use correctly.

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 already provides descriptions for list_id and task_id. The description adds an example and mentions that the task stays in its original list, but does not elaborate further on parameter semantics. Since schema covers the parameters, the description adds moderate value.

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 it adds an existing task to an additional list, distinguishes from moving a task, and notes it does not duplicate but adds membership. It is specific and differentiates from sibling tools like clickup_add_guest_to_list or clickup_add_tag_to_task.

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?

Explicit 'When to Use' and 'When NOT to Use' sections with an alternative (move-task tool) and prerequisite (Tasks in Multiple Lists ClickApp). Provides clear guidance on when to invoke this tool vs alternatives.

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