clickup_delete_view

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

Annotations (destructiveHint=true, idempotentHint=true) are complemented by description stating 'permanently delete' and return type. Adds context about scope (only view, not parent) and error handling. Could mention idempotency implications, but overall good.

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?

Well-structured with clear sections: purpose, when to use/not use, returns, examples, error handling. Front-loaded with key action. No unnecessary 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?

Covers return value (confirmation or error string) and error handling (404). With output schema existing, description is sufficient for a simple delete tool with one parameter.

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 schema description 'View id to delete.' Tool description adds little semantic value beyond the schema, but includes an example usage ('params = {"view_id": "abc123"}') which aids understanding. Adequate but not exceptional.

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 'Permanently delete a task or page view' and distinguishes from sibling delete tools by specifying it only removes the view, not the parent container. Examples of view types (dashboard/board/etc.) further clarify scope.

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?

Explicit when-to-use and when-NOT-to-use sections. Tells when to use (removing a view no longer needed) and when not to use (deleting underlying container) with pointers to other tools. Includes error handling for 404.

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