discord_bulk_ban

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

Goes beyond annotations: describes safety pattern (dry_run default), permissions needed, error behavior (whole call fails if no user banned), return data (counts), and max limits (200 users). No contradiction with 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?

Concise yet comprehensive: purpose first, then safety, permissions, return info, and sibling differentiation. Every sentence adds value with no redundancy.

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 5-parameter tool with no output schema, the description covers all relevant aspects: purpose, safe usage, permissions, return values, and error scenarios, making it fully complete for agent decision-making.

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% with descriptions, and the description adds significant value for the dry_run parameter (explaining the preview pattern) and reinforces the max 200 limit for user_ids. Other parameters are adequately covered by schema; thus better than baseline 3.

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 it bans many users in a single call, intended for raid mitigation, and explicitly distinguishes itself from discord_ban_member for single bans 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: use dry_run to preview, then re-call to actually ban; requires Ban Members and Manage Server permissions; and suggests discord_ban_member for finer control. Includes both when-to-use and when-not-to-use.

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