clickup_guest_remove

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

Without annotations, description fully discloses: permanent action, deletion of share-records, inability to log in, irreversibility, plan restriction, and return type (empty object). No contradictions.

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 concise sentences, front-loaded with key action, no redundant information, every sentence adds value.

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 all critical aspects: action, consequences, prerequisites (plan), return value, and references to sibling tools. Adequate for the tool's complexity.

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 already provides detailed descriptions for both parameters (guest_id and team_id) with 100% coverage. The description reinforces effects but adds minimal new information beyond 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?

Clearly identifies the action as permanently revoking a guest user's access, with specific verb 'revoke' and resource 'guest user'. Differentiates from siblings like clickup_guest_update (modify) and clickup_guest_invite (add).

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 destructive/irreversible nature and provides alternative tool for re-invitation (clickup_guest_invite). Also mentions Enterprise plan requirement, guiding appropriate use cases.

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