Create AutoMod rule

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

The description discloses that rules run on Discord's infrastructure, explains action limitations (timeout unavailable on spam/keyword_preset/member_profile), and clarifies that blocking on member_profile quarantines the member. Since annotations only indicate readOnlyHint=false and destructiveHint=false, the description carries the burden and does so well.

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 long but information-dense, covering multiple trigger types, actions, and constraints without repeating the schema verbatim. It is structured with clear sentences and semicolons, earning its length for a tool with 14 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?

Given the tool's complexity (14 params, no output schema), the description covers operational context, trigger categories, action options, and usage preferences. It does not mention return values, but this is a minor gap for a creation tool where the outcome is implied.

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 description adds semantic value beyond the schema by explaining why presets are useful ('Discord maintains the word list, so none needs to be written') and detailing how actions behave across trigger types. With 71% schema coverage, the description fills gaps and deepens understanding of parameter interactions.

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 tool creates a server-side moderation rule, enumerates all trigger types (keyword, keyword_preset, spam, mention_spam, member_profile), and distinguishes it from sibling tools like update_automod_rule and delete_automod_rule by focusing on creation.

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?

Provides explicit guidance: 'For slur or hate-speech filtering prefer trigger keyword_preset with the slurs preset' and notes that member_profile is for Community servers only. Also gives important constraints like timeout not being available on certain triggers, though it doesn't explicitly contrast with updating/deleting rules.

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