atlasent_delete_webhookDelete a webhook registration by providing its webhook ID and the organization ID that owns it.
Remove a registered webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| org_id | Yes | Organization ID that owns the webhook. | |
| webhook_id | Yes | ID of the webhook to delete. |
Changes observed during successful MCP inspections.
v2.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already set destructiveHint to true, so the agent knows this is destructive. The description adds 'Remove' which aligns. No additional behavioral traits (e.g., cascading effects, reversibility) are disclosed. With annotations covering the main safety concern, a 3 is reasonable.
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?
Single sentence 'Remove a registered webhook.' is highly concise and front-loaded. No wasted words.
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 deletion by ID, the description is adequate but minimal. No output schema exists, and no context about effects or confirmation is provided. Given the tool's simplicity, it meets the minimum viable level.
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 100%, so parameters are fully documented in the schema. The description does not add any extra meaning beyond the schema's property descriptions. Baseline 3 applies.
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 'Remove a registered webhook.' which clearly identifies the action (remove) and resource (webhook). However, it does not distinguish from sibling tools like 'atlasent_create_webhook' or 'atlasent_delete_policy', so a 4 is appropriate.
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?
No guidance on when to use this tool versus alternatives. With siblings like 'atlasent_create_webhook' and other delete tools, the description does not specify when deletion is appropriate or mention prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.