webhook_update

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

Annotations indicate idempotentHint=true, and the description confirms the update is idempotent (PUT). It adds that the body is flat and at least one field besides webhook_id is required, which is not in annotations. No contradiction.

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 that are front-loaded with the tool's purpose and key usage rule. Every word adds value.

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?

The description covers the essential aspects for a simple update tool: purpose, partial update behavior, required fields. No output schema exists, but the return value is not critical for a mutation tool. 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?

Schema coverage is 89%, so the schema already documents most parameters. The description goes beyond by stating the update is partial and the body is flat, clarifying the usage pattern for the webhook_id and required updatable fields.

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 explicitly states 'Update a webhook (PUT /webhooks/{id})' and clarifies it is a partial update. This clearly distinguishes it from webhook_create or webhook_delete. The verb 'update' and resource 'webhook' are specific.

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 advises 'Partial — supply ONLY the fields to change' and 'At least one updatable field besides webhook_id is required', which guides the agent on how to use the tool. It implicitly indicates when to use (update existing webhook) but does not explicitly mention when not to use or alternatives. Sibling names provide enough context.

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