clickup_webhook_create

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

With no annotations, the description carries full burden. It discloses that the tool registers an endpoint that receives POST events, optionally scoped, and returns a secret for signature verification. However, it does not mention authorization requirements, rate limits, or behavior on failure, leaving some gaps.

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 three sentences, front-loaded with the core purpose, then optional scoping, then a critical note about the secret. Every sentence provides necessary information without redundancy.

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 no output schema and no annotations, the description is fairly complete: it covers the action, scoping options, and a key return field (secret). It lacks details on authentication requirements or retry behavior, but these are not critical for a create tool.

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?

Input schema covers all 7 parameters with descriptions (coverage 100%). The description adds value beyond schema: it clarifies scoping mutual exclusivity ('Optionally scope...'), the 5-second response requirement for endpoint, and the secret for verification. This extra context benefits agent understanding.

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's purpose: 'Register an HTTPS endpoint that ClickUp will POST events to'. It mentions optional scoping to space/folder/list/task, which distinguishes it from siblings like clickup_webhook_delete, clickup_webhook_list, and clickup_webhook_update.

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 explains how to scope the webhook ('Optionally scope the webhook to a single space, folder, list, or task') and notes the 5-second response requirement in the endpoint parameter. It implies when to use (create) versus other webhook operations but does not explicitly state alternatives or when not to use.

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