Delete a webhook

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

Annotations already signal destructiveHint=true and readOnlyHint=false, and the description adds valuable context by stating that dependent event flows stop receiving events immediately. This goes beyond the binary annotation and alerts the agent to the cascading irreversibility of the action.

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 short sentences with no filler. The core action is front-loaded, and the second sentence adds a critical behavioral consequence without redundancy.

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 single-parameter destructive operation with an existing output schema and annotations covering safety, the description is complete. It explains the action, the immediate effect, and there is no missing information an agent would need to invoke it correctly.

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?

With 0% schema description coverage, the description should compensate by explaining the webhookId parameter, but it does not mention it at all. The parameter name is self-explanatory and the schema defines it as a required string, but the description adds no value about its meaning or how to obtain it.

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 states a specific verb and resource, 'Delete a webhook endpoint,' which clearly distinguishes it from sibling tools like create_webhook and update_webhook. It also adds a meaningful consequence that reinforces what the operation does.

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 clearly implies this tool is used when an existing webhook needs to be removed, and the immediate effect warning provides useful decision context. It does not explicitly name alternatives or when not to use it, but the purpose is unambiguous enough that an agent can infer correct usage.

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