wrike_delete_folder

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

Despite having no annotations, the description adds an important behavioral detail: the folder is moved to Recycle Bin rather than permanently deleted. This reveals the non-destructive nature of the operation, though it does not mention permissions, idempotency, or effects on child items.

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 that directly states the action and key behavior. Every word contributes value, with no repetition or filler.

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?

For a simple one-parameter delete operation, the description is largely complete: it identifies the target resource, the action, and the notable outcome (move to Recycle Bin). It lacks return-value details, but given the low complexity and high schema coverage, this is not a significant gap.

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% coverage, with folderId described as 'Folder ID (required)'. The description does not add further semantic detail about the parameter beyond what the schema already provides, so the baseline score of 3 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 uses a specific verb ('Delete') with a clear resource ('folder') and adds a meaningful qualifier ('moves to Recycle Bin'), which distinguishes this from other delete tools in the sibling list and clarifies the soft-delete behavior.

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 explicit usage guidance is provided. The description does not state when this tool should be used versus alternatives (e.g., deleting a space or task), and there are no prerequisites or exclusions mentioned.

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