discord_kick_member

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

With no annotations, the description carries the full behavioral burden. It discloses one useful operational behavior: that confirm=true may be required when confirmation is enabled. However, it stays silent on permissions needed, whether the kick is reversible, and how failures are surfaced — significant gaps for a member-removal mutation.

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, front-loaded with the core action. The confirmation requirement earns its place because it triggers a critical parameter decision.

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?

Despite having an output schema, the definition is incomplete for an operation of this weight: it does not explain which guild the member is removed from when guild_id is null, how the confirmation gate is enabled, or any failure behavior. With zero schema parameter descriptions and no annotations, the text leaves too much for the agent to infer.

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 for the four parameters, but it only vaguely touches the confirm parameter and ignores reason, guild_id, and member_id semantics. The schema alone provides names, types, and defaults, yet the description adds practically no meaning beyond what is already structured.

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 states a specific action and target ('Kick a member from the guild'), which is immediately distinguishable from siblings like discord_ban_member, discord_timeout_member, and discord_unban_member. It does not explicitly name or contrast these siblings, but the verb 'kick' makes the intent unambiguous.

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 usage context is implied: this tool is for removing a member temporarily (as opposed to banning or timing out), but the description never states when to choose kick over ban or gives any exclusions. The confirmation note is an operational requirement, not an explicit routing guideline.

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