clickup_user_remove

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

Describes destructive nature, immediate loss of access, preservation of historical records, and return value (empty object). With no annotations, the description fully discloses behavioral traits.

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?

Three sentences efficiently convey purpose, consequences, and alternative. No unnecessary words, front-loaded with verb.

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?

Covers action, parameters, consequences, and return value. Could benefit from mentioning required permissions, but given tool simplicity, it is adequate.

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 detailed parameter descriptions in the schema itself. The description does not add new parameter information beyond what is in the schema, so baseline of 3 applies.

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?

Description clearly states the action: 'Remove a member from a ClickUp workspace, freeing their paid seat.' It distinguishes from siblings by mentioning clickup_user_invite for re-adding, providing specific verb and resource.

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 mentions when to use an alternative (clickup_user_invite for re-adding). However, does not explicitly state when not to use (e.g., cannot remove the workspace owner), though this is covered in the parameter schema.

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