Create Auto Moderation Rule

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

Description aligns with annotations (non-read-only, non-destructive). It notes return details but lacks permissions, side effects, or error conditions. Annotations supply behavioral safety hints.

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?

Well-structured with headings, Arg list, and Returns. Mostly concise, though the Arg list partially duplicates schema. First sentence is clear and front-loaded.

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?

Covers all inputs, but lacks output schema for return value structure and missing prerequisites like required permissions. Reasonably complete given complexity, but could be improved.

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 description coverage is 100%, so the schema already explains parameters. The description rephrases minimal context but adds little beyond defaults or optionality already in schema.

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 verb 'Create' clearly states the action, and 'automod rule' specifies the resource. It distinguishes from sibling tools like discord_edit_automod_rule, discord_delete_automod_rule, etc.

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 explicit guidance on when to use vs alternatives (e.g., editing or listing rules). Usage is implied by the tool name and description, but no direct comparison.

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