clickup_user_remove

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

With no annotations provided, the description carries full burden and excels. It discloses destructive nature ('Destructive'), immediate access loss, data preservation ('assignments and comments are preserved as historical records'), and return value ('Returns an empty object on success'). This covers critical behavioral traits 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?

Four tightly packed sentences with zero waste. Each sentence adds critical information: purpose, destructiveness/data handling, alternative tool, and return value. The structure is front-loaded with the core action.

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 mutation tool with no annotations and no output schema, the description provides complete context. It covers purpose, guidelines, behavioral consequences, parameter context, and return value. No gaps exist given the tool's complexity and lack of structured metadata.

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%, providing a baseline of 3. The description adds value by explaining the business impact ('freeing their paid seat') and re-addition process, which contextualizes the parameters' purpose beyond their technical definitions in the schema.

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 ('Remove a member from a ClickUp workspace') and resource ('member'), distinguishing it from siblings like clickup_user_invite and clickup_user_update. It goes beyond the tool name by specifying the effect on paid seats.

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?

Explicitly states when to use this tool ('to remove a member') and when not to ('Cannot remove the workspace Owner' in schema). It names an alternative for re-adding (clickup_user_invite) and provides prerequisite tools for obtaining IDs (clickup_workspace_list, clickup_member_list).

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