logout_user

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

The annotations already signal a non-read-only, non-idempotent mutation, and the description adds the scoping detail that only the current user session is affected. It does not go further to disclose side effects like session invalidation, required re-authentication, or effects on running applications, but the annotations lower the burden enough for this to be adequate.

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 a single short sentence with no filler and no repeated information. Every word contributes to the meaning, and the action is front-loaded at the start.

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 no-parameter, no-output-schema action, the description captures the core operation completely enough to invoke the tool correctly. It could be more complete by stating post-conditions such as session termination and re-authentication, but the low complexity keeps the gap small.

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?

There are zero parameters and 100% schema coverage, so there is no parameter meaning left for the description to clarify. The phrase current user session correctly indicates that targeting is implicit rather than parameterized, matching the baseline of 4.

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 names a specific verb, log out, and a specific resource, the current user session, so an agent can tell exactly what action is exposed. It is not a tautology and is distinct from all sibling tools, none of which provide a logout action.

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 clearly by the action itself: call this tool when the current user session should be ended. However, it provides no explicit when-to-use or when-not-to-use guidance and does not mention prerequisites such as an active session or what to do if already logged out.

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