clickup_create_task

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

No annotations are provided, so the description carries the full burden. It conveys the write nature and the list prerequisite, but says nothing about permission requirements, failure behavior, or what happens when list_id is invalid. For a 15-param mutation tool this leaves the agent with real gaps.

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 tight sentences, no filler, and the required-input constraint plus prerequisite are front-loaded before the optional capability notes.

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 create tool with no output schema and no annotations, the description covers the essentials and the schema handles the rest. Return shape and error behavior are absent, but they are minor given the schema richness.

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 coverage is 93%, so the schema already documents most parameters in depth (including the extensive custom_fields value formats). The description adds a little on assignees (emails/usernames/"me") and task_type by name, though the assignee claim slightly conflicts with the schema's 'use clickup_resolve_assignees to convert'. Baseline 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?

States a specific verb and resource ('Create a task in a ClickUp list') and immediately names the two required inputs, distinguishing it from siblings like create_list, create_folder, and update_task without opening a schema.

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?

Gives an explicit prerequisite workflow ('always ask the user which list') and names the required fields. It doesn't cover when to use this vs. update_task or move_task, but the create-vs-update distinction is implied strongly enough by the verb.

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