create_list

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the lack of API space creation but does not disclose crucial aspects like authentication requirements, whether the operation is idempotent, or what happens on failure (e.g., duplicate list name). The return value is also not described.

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 extremely concise at two sentences, with the core purpose stated first. Every word adds value, and the secondary sentence provides critical context about name-based lookup and API limitations.

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 8 parameters and no output schema, the description should cover more than just space handling. It omits explanations for other parameters like content, dueDate, priority, assignee, and status, and does not describe the return value (e.g., the created list's ID or details). This leaves significant gaps for agent decision-making.

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?

While the input schema already describes all parameters (100% coverage), the description adds value by explaining the relationship between spaceId and spaceName, and the limitation that space creation is not supported. This context aids the agent in parameter selection.

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 action ('Create a new list') and the resource ('in a ClickUp space'). It distinguishes from sibling tools like create_folder and create_list_in_folder by specifying it creates a list directly in a space, not in a folder.

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 provides useful guidance on using spaceName for name-based lookup, eliminating the need for spaceId. It also explains the limitation that space creation is not supported via API. However, it does not explicitly guide when to use this tool versus create_list_in_folder for nested lists under folders.

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