Ban member

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

Discloses that the first call changes nothing and returns a preview and confirm_token, adding significant context beyond the destructiveHint annotation. No contradictions.

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?

Three concise sentences with no fluff. Front-loaded with the primary action, then covers edge cases and usage pattern.

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 the essential behavior and special cases. Could mention required permissions or what the preview contains, but is largely complete given the tool's complexity and annotations.

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?

Adds context for the user parameter (works on users who left) and explains the dry_run/confirm_token flow. Schema coverage is 50%, but description compensates well for the critical 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?

Clearly states the tool bans a user, with optional message deletion. Distinguishes from siblings like kick_member and bulk_ban by noting it works even if the user has left.

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?

Explicitly describes the safe two-step calling pattern: first call is a preview, second call with confirm_token performs the ban. Does not mention when not to use it, but provides clear usage context.

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