tasks_update_bulk

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

No annotations are provided, so the description carries the burden. It discloses that the tool modifies tasks ('Update'), that each entry requires a task_id, and that it supports batch operations and up to 50 tasks. However, it does not address failure behavior, atomicity, permissions, or the return payload. The continue_on_error parameter exists in the schema but is not explained in the description, and its implications for partial failures are not disclosed. This is adequate but not comprehensive.

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 exactly three sentences, immediately stating the core purpose in the first sentence. It then specifies the key requirement (task_id) and gives concrete batch examples, ending with the limit. Every sentence earns its place with no redundancy or filler.

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 bulk update tool with a nested array schema and no output schema, the description covers the essential aspects: purpose, required field, common batch patterns, and limit. It is missing some details like error handling semantics (though continue_on_error is in the schema, its behavior is not elaborated) and what the operation returns. However, the description is sufficient for an agent to select and invoke the tool correctly in most scenarios.

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 the baseline is 3. The description adds value by explaining how parameters are typically used: 'Can batch-change status across tasks (set status per task), batch-reassign (set assignees array per task), or batch-add tags (set tags array per task).' This clarifies the intended combinations and semantics, going beyond the raw schema field descriptions. It clearly states the requirement for task_id within each update entry.

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 uses a specific verb+resource: 'Update multiple existing ClickUp tasks in a single operation.' It clearly distinguishes from the sibling tool tasks_update (singular) and other bulk tools like tasks_create_bulk by emphasizing the 'multiple tasks' and 'bulk' nature. The purpose is unmistakable.

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 gives clear context for when to use the tool: 'Update multiple existing ClickUp tasks in a single operation' and describes specific batch use cases (status, assignees, tags). It does not explicitly mention alternatives or say when not to use it, but the context implies that it is for bulk updates as opposed to single-task updates via tasks_update. The 50-task limit is also stated, which guides usage.

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