delete_webhook

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the deletion is permanent ('cannot be undone') and that the webhook 'will stop receiving events immediately,' covering the most critical behavioral traits: destructiveness and immediacy. This is transparent and sufficient for a delete operation.

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 two sentences long, front-loaded with the action, and every sentence adds value. The first sentence states the purpose, the second explains the immediate effect and permanence. There is no filler or 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 simple delete operation with three parameters, no output schema, and no nested objects, the description is complete. It specifies the action, the permanent nature, and the immediate consequence. No additional context is needed for an agent to correctly select and invoke this tool.

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 input schema has 100% description coverage for all three parameters (owner, project, webhook_id), so the baseline is 3. The description does not add additional meaning beyond what the schema already provides; it simply reaffirms that the webhook belongs to a project. No further parameter details are given.

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: 'Permanently delete a webhook from a project.' It uses a specific verb (delete) and resource (webhook), distinct from sibling tools like get_webhook, create_webhook, or update_webhook. The additional context about immediate effect and irreversibility further clarifies the tool's unique role.

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 implicitly conveys when to use this tool: when a webhook should be permanently removed and stop receiving events. It does not explicitly mention alternatives or when not to use it (e.g., temporary disable via update_webhook), but the context is clear for a straightforward delete operation.

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