Delete Auto Moderation Rule

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

The annotations already indicate destructiveHint: true. The description adds that the tool returns a 'Confirmation of deletion', but does not elaborate on irreversible consequences or permission requirements. It adds only minimal behavioral context beyond the annotations.

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 extremely concise: one purpose sentence, an args list, and a returns line. It is front-loaded with the purpose and contains no extraneous 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 destructive action, the description covers the core operation and return value. However, it lacks context about required permissions, error handling, or how the confirmation is structured. Still, it is largely sufficient given the annotations that already signal destructive behavior.

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 covers both parameters with descriptions, patterns, and length constraints (100% coverage). The description merely repeats the same information without adding new semantics or examples, so it meets the baseline but does not improve clarity.

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 'Delete an auto moderation rule from a server', specifying the action (delete) and the resource (auto moderation rule). It effectively distinguishes this tool from sibling tools like create, edit, get, and list.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., required permissions), and no conditions for use. It only states the action and arguments.

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