kick_player

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

No annotations provided, but description discloses atomicity via state_lock and the effect (connection returns to IN_LOBBY). Could mention reversibility or side effects.

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?

Concise, structured with clear sections. Every sentence adds value. No extraneous 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 prerequisites (host-only, pre-game), effect, and atomicity. Missing mention of whether action is reversible or how to get connection_id.

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 0%, description does not explain connection_id parameter beyond its name. Agent may not know how to obtain it.

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 verb 'kick', resource 'joiner (slot B)', and host-only constraint. Distinct from siblings like leave_room and join_room.

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 pre-game only (WAITING_FOR_PLAYERS, WAITING_READY) and cannot use during gameplay. However, does not compare to alternatives or indicate when not to use.

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