logoutUser

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

With no annotations provided, the description carries the burden, and it does well by explicitly stating the tool is stateless and that it clears the caller's stored key. This discloses the main side effect and distinguishes server-side vs client-side logout behavior. It could add idempotency or failure behavior, but the core transparency is strong.

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 deliver the action, its stateless nature, and the side effect without any filler. The most important information is front-loaded.

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 tool's zero parameters, no output schema, and simple operation, the description covers everything needed to invoke it correctly: what it does and what state it modifies.

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 fully defines the input surface. The baseline for zero-parameter tools is 4, and the description does not need to add parameter detail.

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 ('Sign out') and resource ('current session'), and adds the defining side effect ('Clears the caller's stored key'). This makes the tool unmistakable and distinguishes it from login/session-related siblings.

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 by the action itself: call this to end the current session. However, there is no explicit guidance about when to prefer it over other auth-related tools, such as whether it should follow requestOtp/validateOtp or what to do when no session exists.

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