clickup_chat_channel_delete

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

Even without annotations, the description fully discloses the tool's behavior: it is destructive, irreversible, cascading (deletes messages and replies), removes the channel for all members, and returns an empty object. This exceeds transparency expectations.

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?

The description is two sentences plus parameter details, all front-loaded with key information. Every sentence serves a purpose: stating the action, emphasizing destructiveness, advising user confirmation, and specifying the return 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?

Given the absence of an output schema, the description covers the return type. It fully explains the tool's effects, prerequisites (user confirmation), and scope (workspace-wide). For a delete tool, this is complete.

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?

The description adds significant value beyond the input schema by telling users where to obtain channel_id and team_id (from specific list tools) and reminding that channel deletion cascades to messages. This is crucial for correct usage.

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 tool permanently deletes a ClickUp Chat channel along with all its messages and replies. It uses strong verbs like 'permanently delete', 'destructive', and 'irreversible', making the purpose unambiguous and distinct from siblings like update or get.

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?

The description explicitly instructs to confirm with the user before calling, providing a clear when-to-use guideline. It does not explicitly list alternatives or when not to use, but the destructive nature implies it should be used sparingly. Still, it provides strong guidance.

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