clickup_delete_webhook

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

The description discloses permanent deletion and the lack of a pause feature, reinforcing the destructiveHint annotation. It also specifies the return type (confirmation) and error handling. However, it does not explicitly address idempotency as hinted by idempotentHint, though the example and error handling imply non-idempotent behavior on unknown IDs.

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 well-structured with clear sections (summary, when to use/not use, returns, example, error handling). It is concise yet comprehensive, with 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?

For a delete operation, the description covers all key aspects: purpose, usage guidance, return value, example, and error handling. Annotations already convey destructive and idempotent hints, so no additional behavioral context is needed.

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 input schema already describes the webhook_id parameter as a UUID. The description adds an example value but does not provide significant additional meaning beyond what the schema offers. With schema coverage effectively 100% (the single parameter has a description), the description's contribution is minimal.

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 webhook and stops event delivery. It distinguishes itself from other tools by explicitly noting there is no pause functionality and referencing clickup_create_webhook as the alternative.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections. It advises against using it for temporary pausing and suggests recreating with clickup_create_webhook instead.

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