discord_admin_automod

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description merely repeats the operation list without adding any new behavioral context such as permissions required, permanence of deletion, or effect on existing rules. It adds no value beyond structured fields.

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, efficient sentence that lists all supported operations with no filler or redundancy. It is front-loaded and easily scannable, making it an appropriately concise summary.

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 CRUD tool with no output schema and a generic data parameter, the description is too terse. It omits the parameter relationships (which itemId is needed for get/update/delete), the shape of the data payload, permission requirements, and what the operation returns. The description lacks operational depth.

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 50% (only data and reason have descriptions). The description lists operations but does not explain how itemId, data, and reason map to specific operations, nor how to structure the data payload. It fails to compensate for the missing parameter descriptions.

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 identifies the tool's function as managing AutoMod rules with five specific CRUD operations. It distinguishes itself from sibling admin tools (e.g., discord_admin_channels, discord_admin_roles) by naming the specific resource, AutoMod rules.

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?

Usage is implied by the resource name and operation list, but the description provides no explicit guidance on when to choose this tool over alternatives, nor does it mention preconditions, permissions, or exclusions. It's a minimal viable statement.

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