webhook-update

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

With no annotations, the description must disclose behavioral traits, but it only states 'Updates a webhook'. It does not mention whether the update is partial or full, what fields are affected, authentication requirements, rate limits, or side effects. This is insufficient for an agent to understand the tool's 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 very concise (one sentence plus a tag), front-loading the action and resource. However, it could include a bit more context without becoming verbose. The structure is efficient.

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?

Given the complexity (3 required parameters, nested requestBody, no output schema), the description is incomplete. It does not explain what fields can be updated, whether the operation is idempotent, or what the response looks like. This leaves significant gaps for an agent.

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 33% (only requestBody has a description). The tool description adds no meaning beyond the schema; it does not explain the purpose of workspacePublicId, webhookPublicId, or the individual fields within requestBody (name, url, secret, events, active). This leaves the agent guessing about parameter usage.

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 ('Updates') and the resource ('a webhook by its public ID'). This directly distinguishes it from sibling tools like webhook-create, webhook-delete, webhook-list, and webhook-test.

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 implies that the tool is used to modify an existing webhook, but it provides no explicit guidance on when to use it versus alternatives, nor any prerequisites or conditions. The context is clear but lacks depth.

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