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

With no annotations and no description of side effects, the agent cannot determine if this action is reversible, triggers notifications, or requires specific permissions. The description fails to provide any behavioral context beyond the bare action.

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 extremely short, but conciseness is not achieved because it omits critical information. It is underspecified rather than efficiently informative.

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 complexity of a room-leaving operation and the presence of sibling tools, the description should cover return values, side effects, and prerequisites. It fails to do so, leaving the tool's behavior largely unexplained.

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 single parameter 'member_id' has no schema description, and the tool description does not clarify its purpose (e.g., whose ID it is or whether it refers to the current user). This leaves the agent guessing about valid values.

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 '방에서 나간다' (leaves the room) essentially restates the tool name 'baton_leave' without adding new detail. It does not specify the scope or distinguish from sibling tools like 'baton_kick' which also results in a member leaving.

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 is provided on when to use this tool versus alternatives (e.g., when to leave vs kick, or whether this is for self or others). There is no mention of prerequisites or context.

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