clickup_space_delete

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

Discloses the irreversible, cascading destructive behavior and notes the return value (empty object). With no annotations, this covers key behavioral traits, though it omits authorization requirements or rate limits.

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?

Two sentences plus an instruction. Every sentence serves a purpose: stating the primary action and its scope, warning about destructiveness, and providing an alternative. No fluff.

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?

For a destructive tool with a single parameter and no output schema, the description covers purpose, usage guidelines, parameter sourcing, and behavioral notes. It could mention required permissions, but overall is sufficiently 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?

Schema has 100% coverage with one parameter. The description adds value by explaining how to obtain the space_id (from clickup_space_list), and reiterates the cascading deletion scope, which the schema's description also mentions.

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 tool permanently deletes a ClickUp space and all its contents. It specifies the verb 'delete' and resource 'space', and distinguishes from sibling tools like clickup_space_update (archival) and clickup_folder_delete (different level).

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 instructs to confirm with the user before calling due to destructiveness. Provides an alternative (use clickup_space_update with archived=true) for reversible hiding, which guides when not to use this tool.

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