slack_kick_from_channel

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

No annotations exist, so the description must cover behavior. It only mentions routing and JWT scope, omitting effects (user removed), permissions needed, or reversibility. The destructive nature is not stated.

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 very short (three sentences), but it lacks essential information. It is concise but not front-loaded with purpose. Some sentences (routing info) are present but not critical.

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's simplicity (kick user from channel) and the presence of an output schema, the description is incomplete. It fails to specify required input fields (channel, user) or behavior, making it hard for an agent to use correctly.

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?

The sole parameter 'arguments' is described only as 'JSON string of arguments for the connector operation', adding no detail beyond the schema. With 0% schema coverage, the description should explain the expected fields (e.g., channel, user).

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 only repeats the name 'kick_from_channel' without explaining the action (removing a user from a channel). It is vague and does not differentiate from siblings like slack_invite_to_channel.

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?

No guidance on when to use this tool vs alternatives (e.g., when to use kick vs invite or archive). No prerequisites or context provided.

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