discord_get_automod_rule

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

Annotations already declare readOnlyHint=true, so 'Read-only' is redundant, but the description adds the meaningful authorization requirement (Manage Server) that is not captured in annotations. What is returned (trigger configuration and actions) is also hinted, though return shape is left to the output schema.

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?

Two tightly written clauses with zero waste; the core action and scope are front-loaded, followed by the permission note.

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?

With an output schema present, the description needn't explain return values, and it covers action, scope, and permission requirement. Complete for a simple two-param read tool, though it doesn't address error or not-found behavior, which is minor here.

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 both guild_id and rule_id are already fully documented in the schema. The description adds only the notion of fetching 'by ID' and provides no syntax or format details beyond the structured data. Baseline 3 is appropriate.

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?

States a specific verb (Fetch) and resource (one AutoMod rule) with scope (by ID, including full trigger configuration and actions). The 'one ... by ID' framing distinguishes it from list_automod_rules and the create/edit/delete siblings without opening any schema.

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 a clear prerequisite ('Requires Manage Server') that guides when the call is valid. However, it does not explicitly name alternatives like list_automod_rules for the case where the ID is unknown, leaving selection partially to inference.

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