clickup_webhook_update

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

No annotations are present, so the description must disclose behavior. It mentions the return value (updated webhook object) and the suspend/resume capability. However, it does not cover potential side effects like whether changing the endpoint immediately stops deliveries or if the new endpoint is tested.

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?

Two sentences, each earning its place: the first states the core action, the second provides a helpful tip. No redundant or extraneous text.

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?

With no output schema, the description adequately notes that the updated webhook object is returned. The 4 parameters are well-documented, and the tip adds practical context. Lacks detail on response field shapes, but acceptable for an update 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?

The input schema already provides full descriptions for all 4 parameters (100% coverage). The description adds value by highlighting the suspend/resume pattern and confirming the return object, slightly elevating it above the baseline of 3.

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 specifies the exact resources affected (delivery endpoint, subscribed events, active status) using a clear verb ('Change'). It implicitly distinguishes from sibling tools (create, delete, list) by focusing on updating existing webhooks.

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 provides a concrete use case: pausing deliveries via status='suspended' and resuming with 'active'. While it doesn't explicitly state when not to use this tool, the sibling context implies create/delete for other lifecycle operations.

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