discord_delete_automod_ruleDelete a Discord AutoMod rule by guild and rule ID, with optional audit reason, confirmation, and backup safeguards for safe server moderation changes.
Delete a Discord AutoMod rule.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| ruleId | Yes | ||
| confirm | No | ||
| guildId | Yes | ||
| backupId | No | ||
| allowWithoutBackup | No |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| error | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds no behavioral context such as irreversibility, permission requirements, or what happens to the rule's configuration.
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?
It is a single, front-loaded sentence with no wasted words. However, it is under-specified rather than appropriately sized for a destructive tool with six parameters.
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 output schema and annotations cover return values and safety hints, but the description omits critical context for a destructive operation: required permissions, the role of confirm/backupId, and consequences of deletion.
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 schema has 6 parameters with 0% description coverage, including non-obvious optional parameters like confirm, backupId, and allowWithoutBackup. The description provides no parameter meaning at all.
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: deleting a Discord AutoMod rule. The purpose is clear, but it does not distinguish this tool from siblings like discord_update_automod_rule or discord_create_automod_rule beyond the verb itself.
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?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implied usage is the literal act of deletion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed