List AutoMod rules

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

Annotations indicate readOnlyHint=true, which covers safety. The description adds minimal context about rules being server-side and includes 'what they do', but does not disclose behavior like output format, pagination, or whether default guild is used when omitted. It does not contradict 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 a single short sentence with no fluff, but it is under-specified. It does not clearly state the tool's action, making it less useful while still being brief.

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 list tool with no output schema, the description should clarify what is returned. 'what they do' hints at content but does not explicitly say the tool returns a list of rules. It is incomplete for guiding an agent on expected results.

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 schema provides 100% coverage with a clear description for the only parameter 'guild'. The tool description does not add parameter details, but the schema already fully documents it, meeting the baseline.

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 'Server-side automatic moderation rules and what they do' explains what the resource is but does not explicitly state the action 'list'. The tool name implies listing, but the description lacks a verb and does not differentiate from sibling tools like create/update/delete_automod_rule.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of viewing rules before creating or updating them, nor any comparison with sibling automod tools.

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