arim_logout

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly reveals the destructive side effects: terminating the session and discarding cookies. This is transparent for a logout operation, though idempotency and error behavior are not covered.

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?

A single, short Korean sentence conveys the complete behavior with no filler or repetition. It is front-loaded with the main action and easy to parse in one line.

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?

For a zero-parameter, no-output-schema logout tool, the description is largely complete: it states what happens to the session and cookies. It omits minor details like post-logout request behavior or behavior when no session exists, but those are not critical for a simple logout call.

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 tool takes zero parameters, so the schema has no properties. The description correctly adds no parameter details, and the baseline for no-parameter tools is 4. No further explanation is needed.

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 ('세션을 종료' = end session, '쿠키를 폐기' = discard cookies) with specific verbs and resources. It inherently differentiates from arim_login and arim_whoami, though it does not explicitly name alternatives.

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 intended use is implied: call when the current session should be ended. However, the description does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites like requiring an active session.

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