discord_bulk_ban

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

Annotations already mark destructiveHint: true and readOnlyHint: false. The description adds valuable behavioral details: dry_run default ensures safety, requires specific permission, and returns counts of banned vs failed users.

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?

Description is brief and front-loaded with purpose. Each sentence serves a distinct purpose: stating mission, safety workflow, permission requirement, return info, and sibling distinction.

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?

Covers key aspects: safety workflow, permission, return value (counts). Missing details about edge cases like already-banned users or nonexistent IDs, but overall sufficient for most use cases.

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 100%, so baseline is 3. The description explains the dry_run parameter's default and purpose, which adds context but does not significantly deepen semantic understanding of other parameters.

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 states the tool's purpose: 'Ban many users in a single call, intended for raid mitigation.' It directly distinguishes from the sibling discord_ban_member by specifying it is for a single ban with finer control.

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 explicit guidance: dry_run safety workflow (call first to preview, then re-call with dry_run:false), required permission ('Requires the Ban Members permission'), and differentiation from the single-ban alternative.

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