Move Task to List

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

Annotations already indicate destructive behavior (destructiveHint=true), but the description does not elaborate on the consequences of moving a task (e.g., removal from the old list, potential status changes). It adds minimal context beyond the annotations, and no details about status mappings or custom field handling are provided.

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 a single, front-loaded sentence that clearly states the primary action. It avoids fluff, though the phrase 'using the v3 API' is mildly redundant filler. Overall, it is efficiently structured but under-informative.

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?

The tool has six parameters, two required, and no output schema, but the description provides only a one-line summary. It fails to explain the effect on the task's current list, the meaning of status mappings, or the purpose of custom field options. The description is far too minimal for a tool with this complexity.

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 0%, so the description must compensate by explaining parameter meaning. It does not mention any of the six parameters or clarify ambiguous ones like 'status_mappings' or 'move_custom_fields.' The description adds no semantic value beyond what the raw schema already exposes.

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 tool's action: 'Move a ClickUp Task to a new home List.' It uses a specific verb (Move) and names the resource (Task) and destination (List). It implicitly distinguishes from sibling 'add_task_to_list' by conveying relocation rather than mere addition.

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 offers no explicit guidance on when to use this tool versus alternatives. It does not mention when moving is preferable to adding, nor any prerequisites or caveats. The phrase 'new home List' hints at the intended scenario, but that is implied rather than stated.

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