clickup_edit_checklist

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

Annotations indicate non-readonly (write operation), non-destructive, and idempotent. The description adds behavioral context by stating it returns a confirmation string with the checklist's name and ID, and notes error handling (404 for missing checklist_id). This complements without contradicting 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 concise, using clear section headings (When to Use, When NOT to Use, Returns, Examples, Error Handling). Every sentence adds value, and the purpose is 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?

Given that an output schema exists (context signal), the description adequately covers return type, error handling, and usage examples. The 3 parameters are well-explained in the schema and examples. Complete for this tool's complexity.

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?

The input schema already provides descriptions for all parameters (name, position, checklist_id). The description adds example usage but no new semantic details beyond the schema. With high schema coverage, a baseline of 3 is 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 it renames and/or repositions a checklist among a task's other checklists. The verb 'Rename' and 'reposition' combined with 'checklist' make the action explicit. It distinguishes from sibling tool 'clickup_edit_checklist_item' which handles individual items.

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 includes explicit 'When to Use' and 'When NOT to Use' sections, providing clear context for when to invoke this tool versus alternatives. It names the specific sibling tool for handling individual items.

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