clickup_checklist_update_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a modification tool (implied mutation) and describes the return value ('Returns the updated checklist object (all items)'), which is helpful. However, it doesn't mention permission requirements, rate limits, error conditions, or whether changes are reversible - significant gaps for a mutation tool with zero annotation coverage.

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 efficiently structured in two sentences: the first states the purpose and capabilities, the second provides sibling tool guidance and return value. Every word earns its place with no redundancy or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description does an adequate job explaining what the tool does and when to use it. However, it lacks important context about authentication requirements, error handling, and the structure of the returned 'updated checklist object.' The description compensates somewhat by mentioning the return type but doesn't fully address the gaps left by missing structured data.

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 100%, so the schema already fully documents all 5 parameters. The description mentions the three modifiable fields (rename, toggle resolved state, change assignee) but doesn't add meaningful semantic context beyond what's in the parameter descriptions. This meets the baseline expectation when schema coverage is complete.

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 specific action ('Modify a single checklist item'), resource ('on a ClickUp task'), and scope ('rename it, toggle its resolved state, or change its assignee'). It distinguishes this tool from its siblings by explicitly mentioning clickup_checklist_add_item and clickup_checklist_delete_item for different operations.

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 provides explicit guidance on when to use this tool ('Modify a single checklist item') versus alternatives ('Use clickup_checklist_add_item to create new items and clickup_checklist_delete_item to remove them'). This clearly defines the tool's specific role among sibling checklist operations.

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