clickup_guest_unshare_folder

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

Discloses cascading behavior (revokes folder-level access to all lists/tasks under it), preservation of separate list/task grants, and the requirement for Enterprise plan. No annotations, so description fully bears the burden.

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 concise sentences, each providing essential information: action, preservation detail, and alternative/requirement. No extraneous 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?

Completely covers the tool's purpose, behavior, parameter sources, return value, and requirements. No gaps given the tool's simplicity and the presence of sibling tools.

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 coverage is 100% with good descriptions for both parameters (how to obtain folder_id and guest_id). The description adds no additional parameter meaning, so baseline score 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?

The description clearly states the action: 'Revoke a guest user's access to a folder' with cascading effect to lists and tasks. It distinguishes from siblings like clickup_guest_share_folder, clickup_guest_unshare_list, etc.

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 (revoke folder-level access while preserving separate grants) and provides an alternative (re-share with clickup_guest_share_folder). Also mentions Enterprise plan requirement.

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