clickup_space_delete

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's destructive and irreversible nature, the cascading impact on all descendant items, and the need for user confirmation. It also specifies the return value ('Returns an empty object on success'), which is crucial given the lack of output schema.

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 front-loaded with the core action and impact, followed by usage warnings and alternatives, and ends with return value information. Every sentence serves a distinct purpose—defining the action, warning about consequences, providing alternatives, and specifying outcomes—with no wasted words.

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 tool's high complexity (destructive, irreversible, cascading) and the lack of annotations and output schema, the description provides all necessary context. It covers the action, risks, user confirmation requirement, alternative actions, and return value, making it complete for safe and effective use by an AI agent.

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 schema description coverage is 100%, so the schema already documents the single parameter 'space_id'. The description does not add any parameter-specific information beyond what the schema provides, but with only one parameter and high schema coverage, the baseline is 3. The description's context about the cascading deletion of descendants adds marginal value, warranting a 4.

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 specific action ('permanently delete'), the target resource ('a ClickUp space'), and the scope ('along with every folder, list, and task inside it'). It distinguishes itself from the sibling tool 'clickup_space_update' by explicitly contrasting deletion with archival.

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 provides explicit guidance on when to use this tool ('confirm with the user before calling') and when to use an alternative ('To hide a space without destroying its contents, use clickup_space_update with archived=true instead'). It also warns about the irreversible nature, helping the agent decide appropriately.

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