Update a webhook

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

The description reveals that setting is_active to false pauses deliveries, but lacks detail on permissions, reversibility, or side effects. Annotations provide no additional behavioral hints.

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 concise sentences with immediate verb and resource identification, no redundant or extraneous information.

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 5-parameter tool with a nested object and no output schema, the description plus schema cover the essential usage. The events parameter schema references an external endpoint, which is adequate.

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 description enumerates key parameters (name, url, events, is_active) and adds partial update context. The schema covers 60% with descriptions, so the description adds meaningful value beyond the schema.

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 action 'Update a webhook subscription' and lists updatable fields, distinguishing it from siblings like create_webhook or delete_webhook.

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?

It explains partial update semantics ('Supply only the fields you want to change') and gives a specific usage hint for is_active, but does not contrast with other webhook-related tools.

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