clickup_add_task_to_list

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

With no annotations, the description carries the full burden and does so well: it discloses the non-obvious multi-homing semantics (home list unchanged, task may not appear in the target list's task query), the paid-feature prerequisite, and the absence of any move API. These are subtle behaviors an agent could not infer from the schema.

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?

Four tightly packed sentences, front-loaded with the core action and immediate correction of the most likely misfire (thinking it moves the task). No filler; every sentence conveys a distinct, decision-relevant fact.

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 two-parameter, annotation-free tool with no output schema, the description covers semantics, prerequisites, failure-to-appear behavior, and the correct alternative workflow. Nothing essential for correct invocation is missing.

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 both task_id and list_id are already documented, including the internal-vs-custom ID format. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

States a specific verb (add), resource (task), and destination (list), plus the crucial scope qualifier 'ADDITIONAL list (multi-homing)'. This clearly separates it from siblings like clickup_create_task (new task) and clickup_remove_task_from_list (detach).

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 says what it is NOT for ('does NOT move the task'), states a prerequisite ('requires the paid Tasks-in-Multiple-Lists feature'), and redirects the move use case to the web UI when no API exists. This is exactly the when/when-not/alternative guidance expected.

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