clickup_guest_unshare_list

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

No annotations provided, so description carries full burden. It discloses immediate loss of access ('destructive'), that the guest account remains, and specifies the Enterprise plan requirement. Returns updated guest object.

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 essential. No filler. Front-loaded with purpose, followed by side effects and requirements.

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 purpose, side effects (guest keeps other grants), destructive nature, reusability (guest account remains), plan requirement, and return value. Complete for a simple revocation tool with no output schema.

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 has 100% coverage with descriptions. Description adds value by cross-referencing how to obtain parameters (e.g., 'Obtain from clickup_guest_get') and clarifying which list's access is revoked.

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 specific list') and distinguishes from siblings by noting that other grants persist and by referencing the complementary tool clickup_guest_share_list.

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?

Provides clear use context: revoking list-level access for a guest. Mentions destructive nature and Enterprise requirement. Does not explicitly list when to use alternatives but contrasts with resumption via share_list.

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