clickup_edit_checklist_item

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

The description discloses behavioral traits beyond annotations: it explains nesting behavior via parent/clear_parent, mentions the return type (confirmation string), and provides error handling (404). Although annotations already indicate non-destructive and idempotent, the description adds practical context without contradiction.

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 well-structured with sections and examples, yet remains concise. The first sentence immediately conveys the tool's purpose, and each subsequent part earns its place without redundancy.

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 tool's complexity (multiple edit actions, nesting) and the availability of an output schema, the description covers return values, error handling, and provides examples. It leaves no significant gaps for an AI agent to understand when and how to invoke the 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 description coverage is 0% (context signal), so the description must compensate. It explains key parameters like parent, clear_parent, resolved, and assignee with examples. However, it does not detail all parameters (e.g., checklist_id, name) beyond what the schema provides, but the usage context adds value.

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 begins with a clear enumeration of actions: 'Rename, (un)resolve, reassign, or nest/un-nest a checklist item.' It specifies the resource (checklist item) and the operations, which distinguishes it from sibling tools like clickup_delete_checklist_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?

Explicit 'When to Use' and 'When NOT to Use' sections are provided. The 'When NOT to Use' section names the alternative tool clickup_delete_checklist_item, offering clear guidance on tool selection.

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