update_webhook

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

There are no annotations, so the description carries the full behavioral disclosure burden. It only reveals that this is a PUT update; it does not explain whether it is a partial or full update, whether disabling is reversible, or what side effects occur. This is insufficient for a mutating webhook endpoint.

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 very short and puts the endpoint upfront, with no filler. 'Update a webhook' is somewhat redundant with the tool name, but the description earns its conciseness by adding the HTTP method and path.

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 tool with 6 parameters, no output schema, no annotations, and many webhook-related siblings, the description is incomplete. It lacks usage context, behavioral expectations, and any response or error information, leaving the agent to rely almost entirely on the schema and surrounding context.

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 description coverage is 83%, and most parameters (url, event, status, extraBody, extraQuery) have meaningful descriptions already. The tool description adds no parameter semantics of its own, so the baseline score of 3 applies given the high schema coverage.

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 a mutation verb and resource ('Update a webhook') and gives the HTTP endpoint, which distinguishes it from sibling tools like create_webhook and get_webhook. It is clear but minimal, offering no detail on what aspects of the webhook can be updated.

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 guidance is provided on when to use this tool versus create_webhook, get_webhook, or list_webhooks. The only signal is the verb 'Update' and the PUT method, which the agent must infer on its own.

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