logout_user

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

The description discloses that the tool removes all active sessions, indicating destructiveness. However, it lacks details on required permissions, immediate effects, or error cases. With no annotations, the description provides basic but incomplete transparency.

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 extremely concise: one sentence for purpose and one for parameter. No superfluous words, and the critical action 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?

The description adequately defines the action but omits return value information (despite an existing output schema) and lacks context about prerequisites or error handling. For a simple tool, it is minimally complete but could improve.

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 description adds meaning to the only parameter 'username' by specifying it is an 'Exact username (email).' This clarifies the required format beyond the input schema (which only defines type string). Schema coverage is 0%, so the description compensates well.

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 tool's action: 'Force logout a user by removing all their active sessions.' This is a specific verb+resource combination that distinguishes it from siblings like 'reset_password' or 'get_user_sessions'.

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?

No guidance on when to use this tool versus alternatives (e.g., get_user_sessions, reset_password). The description does not mention prerequisites, cautions, or exclusions.

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