clickup_checklist_update_item

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

No annotations exist, so description carries full behavioral burden. It explains the net effect (modify fields) and return value (updated checklist object). Does not disclose potential side effects (e.g., notifications, immutability) or error cases.

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 concise sentences: first defines purpose and actions, second links to siblings and return value. No wasted words. Front-loaded with key information.

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 no annotations or output schema, the description adequately covers purpose, ID sourcing, and return value. Missing advanced context like rate limits or error handling, but sufficient for a simple update tool with well-documented input schema.

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?

Input schema has 100% coverage with detailed descriptions. The description adds high-level grouping (three actions) and ID sources, but does not provide new semantic insight beyond the schema. Baseline 3 appropriate.

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 modifies a single checklist item, listing specific actions (rename, toggle resolved, change assignee). It distinguishes from sibling tools clickup_checklist_add_item and clickup_checklist_delete_item.

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?

Provides clear when-to-use (modify existing item) and mentions alternatives for create/delete. Implicitly guides on prerequisites by referencing ID sources (clickup_task_get, clickup_member_list). Lacks explicit when-not or error conditions.

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