delete_webhook

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

No annotations are provided, so the description carries the full burden. It only states 'Delete a ClickUp webhook' without disclosing behavioral traits such as irreversibility, side effects (e.g., stopping events), required permissions, or idempotency. The destructive nature is implied but not explicitly detailed.

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 a single sentence with no filler. It is appropriately sized for such a simple tool, front-loading the action and resource clearly.

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 low complexity (one required parameter, no output schema, no annotations), the description provides the core action but lacks context on the return value or side effects. It is minimally viable but could mention irreversibility or confirmation of deletion.

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 covers the single parameter webhook_id with a description ('The ID of the webhook'), giving 100% coverage. The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 'Delete a ClickUp webhook' uses a specific verb and resource, making it clear that it removes a webhook. It distinguishes itself from sibling tools like create_webhook, update_webhook, and get_webhooks by uniquely specifying the deletion operation.

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 usage is implied by the action 'delete'—it is used when a webhook needs to be removed. However, there is no explicit guidance about when to use this versus alternatives, no prerequisites (e.g., authentication, ownership), and no mention of what happens after deletion.

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