Sign out

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

With no annotations, the description carries full burden of behavior. It clearly states the side effect (removing cached MSAL accounts) which implies signing out disconnects the session. It is honest about what it does, though it doesn't mention whether it clears all auth profiles or just the current session.

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, succinct sentence that conveys the essential purpose. Zero fluff and directly to the point.

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 simplicity (no output schema, one optional parameter), the description is mostly complete. It conveys the effect but omits potential nuances like whether it affects all sessions or only the current one, and whether a subsequent login is required.

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?

Schema coverage is 100% so baseline is 3chers? Actually, the description does not add any information about the tenantId parameter beyond what the schema already provides. The schema already states it defaults to workspace metadata then CPS_TENANT_ID, so the description adds no extra semantics. Thus, a score of 2 is appropriate (lower than baseline because it adds zero value).

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 states a specific action ('Remove cached MSAL accounts') and a clear scope ('for the tenant'), which is clear and actionable. It distinguishes from siblings like cs_login and cs_login_status, though it could explicitly mention that it signs out the current user.

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. It does not mention that it should be used when the user wants to end a session explicitly, nor does it reference any related tools. Without this, an agent may not know if it's needed before auth or after.

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