Update task

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

Annotations already provide readOnly=false and destructiveHint=true. The description adds the partial-update behavior ('only the provided fields'), which clarifies that unspecified fields are preserved. However, it does not disclose side effects such as null handling, status validation, or output behavior. No contradiction with annotations.

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 with no redundant content. It is concise and to the point, though it could be more informative without losing brevity.

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?

Given the complexity of the schema (15 parameters, nested objects) and the absence of an output schema, the description is insufficient. It only states the core action and partial-update behavior, but does not explain how to use the parameters, when to provide workspace_id, or what the response looks like. The agent would need additional external knowledge to invoke this tool correctly.

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%, and the description provides no explanation of any of the 15 parameters, including the nested assignees object, date-time formats, or boolean flags. The description does not compensate at all for the lack of schema descriptions, leaving parameter meanings entirely unclear.

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 verb 'Update', the resource 'ClickUp task', and the scope 'only the provided fields', which distinguishes it from create_task, delete_task, and update_bulk_tasks. This is a specific and useful purpose statement.

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?

No guidance is given on when to use this tool vs alternatives. It does not mention update_bulk_tasks for bulk operations, nor does it describe any prerequisites or exclusions. The description only states what it does, not when to choose it.

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