session_login_as_return

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

No annotations are provided, so the description carries the full disclosure burden. It states the core state transition, leaving the login-as session and returning to admin, but does not mention prerequisites (e.g., an active login-as session), behavior if called outside such a session, or whether the impersonated user's session is affected.

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?

A single concise sentence with no filler. The action and result are front-loaded and every word contributes meaning.

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 zero-parameter tool, the description is nearly complete: it states the action and outcome, and an output schema exists so return-value documentation is not missing. The only gap is the implicit prerequisite of being inside an active login-as session.

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 has zero parameters and an empty schema, so description adds no parameter meaning is necessary. This matches the baseline for no-parameter tools.

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 ('Leave') and resource ('login-as session') with a clear outcome ('return to the admin'). It is immediately distinguishable from sibling session_login_as tools, which enter or manage login-as 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?

The phrasing clearly implies this tool is used when an admin is currently in a login-as session and wants to exit back to admin. It does not explicitly name alternatives or exclusions, but the sibling pair session_login_as / session_login_as_return makes the usage context obvious.

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