wrike_delete_group

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It only states 'Delete a group' without explaining destructive nature, irreversibility, permission requirements, or dependency checks. The 'test' parameter hints at dependency checking but this is not disclosed in the description.

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 'Delete a group', which is exceptionally concise and front-loaded. Every word earns its place, and there is no unnecessary content.

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?

Despite the apparent simplicity, the presence of a 'test' mode for dependency checking suggests important behavioral context that is missing. There is no mention of return values, side effects, or conditions under which deletion is allowed. The description is under-specified for safe use of a destructive operation.

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?

Schema description coverage is 100%, with both parameters having descriptive comments. The tool description adds no additional parameter semantics beyond the schema, so baseline 3 applies. The unusual 'test' parameter is not explained further, but the schema already describes it.

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' and resource 'a group', clearly indicating the operation. It distinguishes from sibling tools like update, create, and get group by naming the delete action, though it doesn't add extra context beyond the tool 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?

No guidance on when to use this tool versus alternatives. There are no prerequisites, conditions, or mentions of related tools. Sibling tools include wrike_delete_custom_status, wrike_delete_attachment, etc., but no comparative or usage context is provided.

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