clickup_move_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It never says what happens on the source side (removal from the old list), whether statuses or custom field values are remapped across lists, what permissions are required, or whether the move is reversible — all material 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?

Two sentences, front-loaded with the action, with no filler. The parenthetical custom-ID note overlaps with the schema slightly but is short enough not to be waste.

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 3-parameter mutation with no annotations and no output schema, the description covers inputs and the name-resolution detour but omits the outcome semantics an agent needs (what changes in the destination list, what is lost). Adequate but with a real gap.

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 coverage is 100%, so all three parameters are already documented, including custom-ID support and the workspace_id conditional. The description merely restates required parameters and duplicates the custom-ID note, adding no syntax or format detail 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?

"Move a task to a new home list" gives a specific verb (move) and resource (task), and the destination is stated. It does not differentiate from close siblings like clickup_add_task_to_list or clickup_remove_task_from_list, so an agent must infer whether this relocates versus adds a secondary location.

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?

It states prerequisites (both IDs required) and routes the agent to clickup_get_list when only a list name is known, which is genuinely useful. It gives no when-not guidance or comparison against add_task_to_list / remove_task_from_list, which is the most likely ambiguity given the sibling set.

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