clickup_view_delete

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

With no annotations provided, the description fully informs the agent about destructiveness ('Permanently delete', 'Destructive and irreversible'), behavior on default views (returns 400), effect on tasks (not affected), and success return (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?

Two sentences convey all essential information without redundancy. The first sentence front-loads the purpose, followed by key behavioral notes. Every word serves a purpose.

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 simple tool with one parameter and no output schema, the description covers all necessary context: destructive irreversible action, default view restriction, no effect on tasks, and empty return on success. No gaps.

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?

Only one parameter (view_id) with 100% schema coverage; the schema description already explains how to obtain it and its constraints. The description adds the view types but adds limited value beyond the schema, meeting the baseline of 3.

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 ('permanently delete') and the resource ('ClickUp view'), listing specific view types (board, list, calendar, gantt). It naturally distinguishes from siblings like clickup_view_update or clickup_view_create, as it is a deletion tool.

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?

It explicitly states that default views cannot be deleted and will return a 400 error, guiding the agent on when to use (only custom views) and when not. It does not name alternative tools but the context of irreversible deletion versus updating (clickup_view_update) is implied.

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