Delete a user group

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

Annotations already declare destructiveHint=true, and the description repeats this by saying 'Removes.' It adds no additional behavioral context such as irreversibility, effects on related resources, or authentication requirements. The description is essentially a restatement of the title and annotations.

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 sentence with no wasted words, and it front-loads the verb 'Removes.' While it is minimal, it is appropriately concise for the simple action, though it could include more detail without losing conciseness.

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 delete operation, the description is incomplete. It does not mention that deletion is permanent, that confirmation is required, or any side effects. The schema and annotations provide some context, but the description itself does not help the agent understand the full impact or prerequisites.

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 provides full descriptions for all three parameters: group_id, confirm (const true), and workspace_id (with fallback logic). The tool description adds no additional parameter meaning, so baseline 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 states 'Removes a team.' which clearly identifies the action (removes) and the resource (a team, synonymous with user group in Clockify). It distinguishes from sibling tools like create_user_group or update_user_group by focusing on removal, though it doesn't explicitly mention the 'user group' term.

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, any prerequisites, or alternatives. It does not warn about the destructive nature or mention that confirmation is required, leaving the agent without context for appropriate invocation.

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