Bulk ban Discord members

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is carried structurally. The description still adds real value by disclosing the 200-user cap, the confirmation requirement, and the backup-or-opt-out gate — details not present in the 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?

Two sentences, zero padding, with the capability and the gating prerequisites front-loaded in that order. Every clause carries information an agent needs.

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 no explanation, and the annotations cover the destructive profile. However, for a seven-parameter destructive bulk operation, the definition omits the message-purge semantics of deleteMessageSeconds and the reason field's audit purpose, leaving notable gaps.

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 coverage is 0%, so the description must compensate, and it only explains three of seven parameters (confirm, backupId, allowWithoutBackup). It says nothing about guildId format, the userIds array bounds, the reason string, or deleteMessageSeconds — the last being a meaningfully destructive option left unexplained.

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 and resource ('Ban ... users') plus the batch scope ('up to 200 users in one Discord request'), which implicitly distinguishes it from the single-user discord_ban_member sibling. It stops short of explicitly naming that sibling, so an agent must infer the distinction.

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?

The preconditions ('Requires confirmation and either a backupId or allowWithoutBackup') hint at when the tool is callable, but there is no explicit statement of when to choose this over discord_ban_member or discord_kick_member, and no warning about irreversibility or rate limits.

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