nworks_logout

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the destructive action (deletion) and scope (all saved auth info and tokens, not just current session), which is the essential behavior for a logout tool. It could be improved by explicitly mentioning that this terminates API access until re-authentication.

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 consists of a single, efficient sentence that immediately states the action and target. There is no redundant text or wasted words; every element earns its place.

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 this is a simple authentication management tool with zero input parameters and no output schema, the description provides complete context by explaining exactly what data is affected (saved credentials) and what action occurs (deletion). No additional context is required for correct invocation.

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 input schema has zero parameters. Per scoring guidelines, zero-parameter tools have a baseline score of 4. The description does not need to compensate for missing parameter documentation.

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 uses the specific verb '삭제합니다' (deletes) with the clear resource '저장된 NAVER WORKS 인증 정보와 토큰' (saved NAVER WORKS authentication information and tokens). It effectively distinguishes from sibling tools like nworks_login_user (which would establish auth) by stating it removes credentials.

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?

While the tool name 'logout' and description imply this is for ending sessions or removing credentials, there is no explicit guidance on when to use this versus simply letting tokens expire, or warnings about losing access to other nworks_* tools that require authentication.

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