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

Beyond the annotations, it discloses immediate token revocation at the identity provider and the session-scoped effect of passing sessionKey. This aligns with idempotentHint=true and does not contradict the read/destructive hints.

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?

Two short sentences front-load the core action and then explain the optional parameter. The only minor redundancy is repeating 'logout/Log out,' but it does not interfere with clarity.

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?

With one optional parameter fully documented and the description covering purpose and scoping, an agent has what it needs to invoke the tool correctly. No output schema is present, but logout's return value is not essential for correct usage.

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 schema already documents sessionKey's format and flow conditions, but the description adds extra meaning by explaining that passing it ends that conversation session. This goes beyond a bare restatement of the schema.

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 a specific verb and resource: it revokes the session's tokens at the identity provider immediately. This clearly distinguishes logout from related auth siblings like loginWithDevice and checkDeviceLoginStatus.

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 description gives conditional context for the optional sessionKey, explaining that it comes from checkDeviceLoginStatus and ends that conversation session. It is clear even though it does not explicitly name alternative tools to use instead.

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