Create Folder

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

The description adds no behavioral context beyond what annotations already provide. It simply restates the action ('create') and does not mention permissions, idempotency, error behavior, or side effects. For a write operation without further disclosure, this falls short.

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, front-loaded sentence with no redundant words. It is concise and immediately understandable.

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?

The tool is a simple create operation, but the description lacks essential context such as return value, permission requirements, or failure scenarios. Since there is no output schema, the description should disclose what the tool returns or whether any side effects occur, but it does not.

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?

With zero schema coverage, the description must compensate. It indirectly clarifies that 'space_id' refers to a ClickUp Space and 'name' is the folder name, but it does not explicitly define either parameter or provide format details. This is minimal compensation, so a middle score 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?

The description clearly states the action (create), the resource (folder), and the context (a ClickUp Space). It distinguishes from sibling tools like create_list_in_space and get_folder by specifying the resource is a folder and the location is a space.

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?

No guidance is provided about when to use this tool versus alternatives such as create_list_in_space or create_list_in_folder. There are no prerequisites, exclusions, or context cues beyond the basic action.

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