clickup_list_create

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

Discloses the mutual exclusivity constraint and return behavior (id provided). However, no annotations exist, so the description should also cover error cases or required permissions, which are omitted.

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 sentences, front-loaded with purpose, no fluff. Every sentence adds essential information.

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?

Covers creation, parent selection, and return value usage. While it doesn't detail error handling or all param effects (e.g., due_date), the schema fills those gaps. Good for a create 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 coverage is 100%, so baseline is 3. The description adds value by explaining the mutual exclusivity and return id usage, enhancing semantic understanding beyond schema descriptions.

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 creates a new task list and specifies the parent context (folder or space). It distinguishes from sibling tools like clickup_task_create by focusing on list creation and returning a new id.

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?

Explicitly states that exactly one of folder_id or space_id must be provided, guiding correct invocation. It also hints at using the returned id for related calls like clickup_task_create, but could add more on when not to use (e.g., alternatives).

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