discord_kick_member

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

Adds context beyond annotations: rejoin possibility, permission requirements, audit log recording. Aligns with destructiveHint=true.

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 each adding value: action, distinction with ban, alternative suggestion. No wasted words.

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 behavior (removal, rejoin), permissions, audit log, and alternative. Complete for an agent to understand execution requirements and outcomes.

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%, baseline 3. Description adds minimal value beyond schema (only mentions audit log for reason). No significant new parameter info.

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 removes a member from a server and distinguishes from ban by noting rejoin possibility and suggesting the sibling tool discord_ban_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?

Explicitly states when to use (non-permanent removal) and when not (use ban for blocking re-entry). Also specifies required permissions and bot role hierarchy.

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