clickup_update_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. It implies a mutation but discloses nothing about permissions, reversibility, or partial-vs-full update semantics, and for a 14-param tool that is a significant gap. The only behavioral disclosure is the assignee add/rem convention.

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 short, front-loaded sentences with no filler. Appropriately terse, though it is perhaps over-brief relative to the tool's 14 parameters.

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 high-complexity mutation tool with nested objects, no annotations, and no output schema, the description is too thin. It omits update semantics (partial vs full), null/unparent behavior, and any safety context an agent would need.

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 86%, above the 80% threshold, so the baseline is 3. The 'assignees use add/rem arrays, not a flat list' note reinforces the nested schema and adds a useful warning, but does not go beyond what the schema already declares.

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+resource ('Update a task') that is clearly distinguishable from the create/delete/get siblings. It does not name or differentiate against any specific alternative, so it stops short of a 5.

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?

There is no guidance on when to use this versus siblings like clickup_create_task, clickup_add_task_to_list, or clickup_set_custom_field. The only other sentence is a parameter note, not usage context.

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