wrike_delete_task

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

The description discloses the key behavioral trait that deletion moves the task to the Recycle Bin rather than permanent destruction, which is valuable for setting expectations. However, with no annotations provided, the description carries the full burden and does not mention permissions, reversibility nuances, or impact on associated data, leaving some gaps.

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 conveys the primary action and key behavioral caveat in just eight words. Every word earns its place, and there is no redundancy or unnecessary detail.

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 tool's simplicity (one required parameter, no output schema), the description is sufficiently complete for an agent to understand the operation and its soft-delete behavior. The Recycle Bin detail is crucial and not obvious from the tool name alone. While missing permission info, it is adequate for the tool's complexity.

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 already provides the parameter 'taskId' with a clear description and 100% coverage. The tool description adds no additional meaning about the parameter, 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 clearly states the action ('Delete') and the resource ('a task'), with the parenthetical '(moves to Recycle Bin)' adding important scope about the behavior. It distinguishes this tool from sibling delete tools like wrike_delete_folder or wrike_delete_attachment by explicitly naming 'task' as the target.

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 no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. While it implies usage for deleting tasks, it lacks contextual direction that would help an agent decide between this and other delete or update tools.

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