create_list

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

No annotations are provided, so the description carries the burden. It discloses a meaningful behavioral precondition: must supply either folder_id or space_id, which is not fully explicit in the schema. However, it does not mention permissions, error conditions, return format, or default behaviors, leaving some transparency gaps for a mutation tool.

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 a single sentence that efficiently communicates the core action and the most important parameter constraint. Every word contributes meaning, and it is front-loaded with the verb and object. There is zero wasted text.

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?

With 9 parameters, no annotations, and no output schema, the description provides the essential context (what and where) and the key either/or requirement. However, it leaves out details like what happens if both folder_id and space_id are provided, response behavior, and any operational prerequisites. It is adequate but not comprehensive.

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 schema provides 100% coverage with descriptions, so baseline is 3. The description adds value by clarifying the relationship between folder_id and space_id ('Provide either...'), which is a semantic constraint not fully captured by the schema's individual field descriptions. This extra clarification justifies a score above baseline.

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's function with a specific verb+resource: 'Create a new list in a ClickUp folder or space.' It also distinguishes itself from sibling tools like get_lists, update_list, and delete_list by specifying 'create' and the container context. No ambiguity.

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 implies usage (when creating a list) but does not explicitly contrast with alternatives such as create_task or update_list. It does provide a key usage constraint ('Provide either folder_id or space_id'), but that is a parameter-level guideline rather than tool-selection guidance. No sibling alternatives named.

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