discord_ban_member

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

Disclosures beyond annotations: permission requirements, role hierarchy, audit log recording, and message deletion behavior. Does not repeat annotations; adds value. Missing details on error handling or idempotent behavior, but annotations already cover idempotency.

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 sentences front-loaded with the primary action, then prerequisites and alternatives. No superfluous content; each sentence earns its place.

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 main action, side effects, requirements, and alternatives. Lacks mention of return value or confirmation, but given the tool's straightforward nature and no output schema, it is reasonably complete.

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. Description mentions 'Optionally bulk-deletes their recent messages' which aligns with the delete_message_days parameter but adds no new information beyond the schema 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 states 'Ban a user from the server, blocking re-entry until unbanned', specifying the verb and resource. It distinguishes from sibling tools by naming discord_unban_member and discord_kick_member explicitly.

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: when to use (banning with optional message deletion), when not (use discord_kick_member for non-permanent), and prerequisites (Ban Members permission, bot role hierarchy).

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