clickup_create_checklist

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

The description adds behavioral context beyond annotations: it states the checklist is empty initially, explains error codes (404, 403) and their meanings, and specifies the return format (confirmation string with name and id). This is valuable context not covered by annotations alone.

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 highly structured with sections (When to Use, When NOT to Use, Returns, Examples, Error Handling) that are concise and valuable. Every sentence adds information, and the main action 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 the tool's moderate complexity (task ID variants, team ID fallback, error handling, relation to other tools), the description covers all essential aspects: purpose, usage boundaries, return type, examples, and error conditions. It is fully adequate for an agent to invoke correctly.

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?

Although the schema descriptions cover parameter basics, the description enriches semantics with usage examples showing different parameter combinations (e.g., custom_task_ids fallback to CLICKUP_TEAM_ID). It also clarifies the team_id requirement when custom_task_ids is True, which is not explicit in the schema.

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 adds an empty checklist to a task, with a specific verb ('Add') and resource ('checklist'). It distinguishes from the sibling tool clickup_create_checklist_item by noting that items are added afterwards, making the purpose unambiguous.

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 explicitly defines when to use (breaking a task into trackable sub-steps) and when NOT to use (for work requiring assignee/due date/status, with the alternative clickup_create_task with parent). This provides clear guidance for tool selection.

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