update_task

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

No annotations provided, so description should disclose mutation behavior and side effects. Only states 'Update an existing task' without detailing permissions, error handling, or behavior on name clashes. Insufficient for a mutation lacking 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?

Two sentences (28 words) efficiently convey main purpose and key feature. No fluff, front-loaded.

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?

With 8 parameters, no output schema, and no annotations, the description should cover more context (e.g., response format, error cases, partial update behavior). Current description is too sparse for a complex update tool.

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% with descriptions. Tool description adds value by highlighting name-based lookup capability and the optionality of taskId/taskName, going beyond schema defaults.

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?

Clearly states the action ('Update') and resource ('existing task in ClickUp') with a distinctive feature ('name-based lookup'). Distinguishes from siblings like create_task, delete_task, get_task.

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?

Mentions name-based lookup as a convenience feature, implying when to use it (when task name is known). However, no explicit guidance on when not to use or alternatives like create_task for new tasks.

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