Ban Discord member

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value by disclosing the confirmation gate and the backup-or-opt-out requirement that annotations do not convey. It stops short of explaining what the confirmation actually does or the consequences of banning (message deletion, reversibility via unban).

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 short sentences with no filler; the action is front-loaded and the precondition follows. It is efficient, though the terseness is part of why key semantics are missing.

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?

Output schema and annotations are rich, so return values and safety need not be repeated. But this is a destructive 7-parameter mutation at 0% schema coverage, and the description leaves the backup workflow, the confirm semantics, and deleteMessageSeconds entirely unexplained — not enough for correct invocation.

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 description coverage is 0%, so the description must carry parameter meaning. It mentions confirm, backupId, and allowWithoutBackup by name but never explains what a backupId refers to or how to obtain one, and says nothing about guildId, userId, reason, or deleteMessageSeconds — especially the 0-604800 message-purge window, which is the most consequential parameter.

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 a guild member'), which is unambiguous. However, it does not distinguish itself from closely related siblings like discord_kick_member, discord_timeout_member, discord_unban_member, or discord_bulk_ban_members, so the agent gets no help choosing among them from the description.

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 description names a precondition ('Requires confirmation and either a backupId or allowWithoutBackup'), which is genuinely useful context for invocation. But it gives no guidance on when to ban versus kick/timeout, nor when the backup path should be preferred over allowWithoutBackup.

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