wrike_create_folder

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a new folder' and does not disclose permissions required, side effects, return behavior, or error conditions. For a mutation tool, this is a significant gap in transparency.

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 short sentence, which is front-loaded and free of fluff. However, it is under-specified and merely restates the tool's name, so it does not earn its place. True conciseness should convey meaningful content with efficient wording, not simply omit necessary 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?

Given the absence of an output schema and annotations, the description should provide more context about the tool's behavior, such as return values, prerequisites, and side effects. It offers none of this, leaving the agent with only the bare statement that it creates a folder. This is inadequate for a complete understanding of the tool's use.

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 input schema has 100% description coverage for all four parameters, so the schema fully documents them. The description adds no parameter-level meaning, but per the rubric, when schema coverage is high, the baseline is 3. The description is not required to explain parameters beyond what the schema already provides.

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 'Create a new folder' is essentially a restatement of the tool name wrike_create_folder, providing no additional specificity about the action or resource. It does not distinguish this tool from sibling tools like wrike_create_space, wrike_create_task, or wrike_create_project, and adds no context beyond the name.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any prerequisites (e.g., needing a parent folder), nor does it provide context on whether this is the appropriate tool for creating projects or spaces instead. No exclusions or alternative tools are referenced.

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