update_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. The description only says 'Change how an existing webhook responds' which implies mutation but doesn't disclose whether updates are immediately effective, whether partial updates are possible (parameters are optional), what happens if invalid values are given, or if there are any side effects. Given that this is a mutation tool with zero annotation coverage, more detail is needed about behavior.

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 concise, two sentences, front-loaded with the purpose. The first sentence covers the main action, the second gives usage guidance. No unnecessary fluff. Could be structured slightly better by mapping the listed aspects to parameter names, but it's passable.

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 6 parameters, low schema coverage, no annotations, and a complex mutation operation, the description is incomplete. It doesn't explain the semantics of parameters like default_status vs default_content, whether all parameters are optional (though the schema shows defaults null, so likely), what the output schema contains (though output schema exists, so that helps), or how updates are applied. Given the tool's complexity and lack of structured metadata, the description should provide more context. However, the output schema reduces some burden about return values.

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 only 17% (only webhook_token has a description). The tool description adds a list of fields it can change: status, body, timeout, CORS. However, it doesn't map these to the actual parameter names (default_status, default_content, default_content_type, timeout, cors). The description uses generic terms that roughly correspond but cause ambiguity. With 6 parameters and low schema coverage, the description should do more to clarify each parameter's meaning. It's borderline minimum viable.

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 changes 'how an existing webhook responds' and lists the specific aspects: status, body, timeout, and CORS. This distinguishes it from sibling tools like create_webhook (creation) and send_to_webhook (sending requests). It could be more explicit about it being an update to a specific pre-created webhook, but the mention of 'existing webhook' and webhook_token clarify that.

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 explicitly says 'Use after create_webhook when the user wants a different canned reply.' This provides clear guidance on when to use the tool and implies a prerequisite (webhook must already exist). It doesn't explicitly exclude alternatives, but the context of sibling tools makes it obvious. The guidance could mention that other tools like get_webhook_info are for reading, not updating, but it's adequate.

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