Update Discord AutoMod rule

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is communicated structurally. The description adds no behavioral context beyond the annotations: it does not explain what gets overwritten, whether omitted fields are preserved, or why a confirm parameter exists despite the destructive operation.

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 a single front-loaded sentence with no wasted words. However, for an 11-parameter destructive update tool, this level of brevity becomes under-specification rather than effective conciseness.

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?

An output schema exists, so return values need not be explained, and annotations cover safety traits. Still, the description is incomplete for a destructive 11-parameter update with nested trigger metadata and actions, and provides almost no help on parameter usage or update semantics.

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 0%, so the description must compensate for 11 undocumented parameters. It only mentions triggerMetadata and actions, leaving guildId, ruleId, confirm, reason, enabled, eventType, and exemption lists entirely unexplained. This is far from sufficient for a nested destructive update operation.

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: 'Update a Discord AutoMod rule.' It also names two key areas, JSON trigger metadata and actions, which helps distinguish this from create/list/delete siblings. It stops short of fully describing the update scope, but the core purpose is clear.

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 discord_create_automod_rule, discord_delete_automod_rule, or discord_list_automod_rules. The description does not mention prerequisites, required permissions, or the meaning of the confirm parameter.

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