clickup_group_delete

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

With no annotations provided, the description carries the full burden and excels. It explicitly discloses critical behavioral traits: the operation is 'destructive and irreversible', clarifies side effects (historical records remain, individual users unaffected), and specifies the return value ('empty object on success'). This provides comprehensive behavioral context beyond basic functionality.

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 perfectly front-loaded with the core action, followed by critical warnings and side effects, ending with return value. Every sentence earns its place with zero waste. The structure efficiently communicates essential information in minimal space.

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 destructive deletion tool with no annotations and no output schema, the description provides complete context: purpose, behavioral warnings, side effects, and return value. Given the complexity of a permanent deletion operation, it addresses all necessary aspects an agent needs to understand the tool's impact and usage.

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 one parameter (group_id), so the baseline is 3. The description doesn't add parameter-specific details beyond the schema, but it reinforces the tool's purpose which helps contextualize the parameter. Since there's only one parameter and the schema already documents it well, a score of 4 reflects adequate contextualization without redundancy.

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 specific action ('permanently delete') and resource ('ClickUp user group'), distinguishing it from sibling tools like clickup_group_create, clickup_group_list, and clickup_group_update. It precisely defines what gets deleted without ambiguity.

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 implies usage context by mentioning that assignments and mentions remain as historical records, but it doesn't explicitly state when to use this tool versus alternatives or provide prerequisites. No explicit guidance on when-not-to-use or comparisons with other deletion tools is given.

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