kick_member

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

The description lacks any behavioral context such as permissions required, whether the kick is reversible, or any side effects. With no annotations available, the description must carry the burden, but it fails to disclose any behavioral traits.

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?

The description is a single sentence, which is concise, but it lacks structure and detail. It is front-loaded with the purpose but at the cost of completeness. Minimal information is provided, but it is not excessively verbose.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is severely incomplete. It does not cover return values, error handling, or any operational nuances. The context signals indicate high parameter count and low coverage, but the description does not compensate.

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%, meaning no parameters have descriptions. The description does not add any meaning beyond the schema. For example, the 'reason' parameter is not explained in terms of format or purpose. The description provides no parameter information.

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 the action 'Kick a member from the guild.' It identifies the verb and resource, and from the sibling list it is distinguishable from related tools like ban_member or timeout_member. However, it does not explicitly differentiate its purpose from those siblings.

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?

There is no guidance on when to use this tool versus alternatives such as ban_member or timeout_member. No context about prerequisites, restrictions, or when not to use it is provided.

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