Kick Discord member

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

Annotations already flag the operation as destructive, non-idempotent, and open-world. The description adds useful behavioral context by stating that confirmation is required and that a backup or explicit no-backup allowance is needed, which materially affects how an agent should invoke it.

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, front-loaded with the action and then the mandatory conditions. No wasted wording.

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 destructive moderation tool, the description gives essential gating conditions but omits permission requirements, expected effect details, and how kick compares with sibling moderation actions. The output schema exists, so return values need not be described.

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 compensate. It explains the conditional relationship around confirm, backupId, and allowWithoutBackup, but leaves reason and the exact semantics of backupId and guildId/userId unaddressed beyond their names.

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: "Kick a guild member." This is clear, though it does not explicitly distinguish the action from sibling tools such as ban_member or timeout_member.

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 a key prerequisite: confirmation and either backupId or allowWithoutBackup. However, it does not explain when to choose kick over ban, timeout, or other moderation actions, nor when a backup is appropriate versus bypassing it.

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