create_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 of behavioral disclosure. It doesn't state that creating a webhook persists a subscription, that events will be POSTed to the endpoint, that the endpoint must be publicly accessible/HTTPS, that there are rate limits or delivery retries, or what happens on failure. The security implication of exposing an endpoint and the ongoing nature of the subscription are not disclosed. This is a meaningful gap for a creation tool with zero annotation coverage.

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 concise sentence with zero wasted words. It's appropriately front-loaded with the core purpose. However, given how much behavioral and usage context is missing, additional sentences would have been warranted—brevity here borders on under-specification rather than genuine conciseness in service of clarity.

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 creation tool with 7 parameters, no annotations, and no output schema, the description should do substantially more. The events/schema combination gives good parameter-level detail, but nothing covers setup requirements (public HTTPS server, authentication/verification of the webhook), what the response returns (webhook ID? secret?), or lifecycle management guidance. Completion isn't required—the description is inadequate for an agent to confidently set up and verify a webhook.

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?

Schema coverage is 100%, so the schema already documents all 7 parameters well, including the full enum list for events. The description adds the key semantic detail that ['*'] subscribes to all events, which is valuable shorthand beyond the schema. The behavioral scope options (list_id, task_id, space_id, folder_id) are named in the schema but their mutually-exclusive or combinable nature isn't clarified, though this is minor given strong schema coverage. Baseline 3 + bonus for the wildcard note = 4.

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 'Create a webhook to receive real-time ClickUp events' clearly states the verb (create), resource (webhook), and purpose (receive real-time events). It distinguishes from siblings like get_webhooks, update_webhook, and delete_webhook, which are clearly different operations. A 5 would require more specific scope detail (e.g., what entities can be subscribed), but the core purpose is clear.

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?

No when-to-use or when-not-to-use guidance is provided. The description doesn't explain when to choose this over alternatives, how webhooks compare to polling via get_tasks, or what the endpoint needs to be prepared to handle. No exclusions or prerequisites (like public HTTPS requirement or server setup) are mentioned. Sibling tools like get_webhooks/update_webhook imply lifecycle context but that's not conveyed.

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