logout

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

With no annotations, the description carries full responsibility. It discloses that it clears auth, pending confirmations, and offers; disconnects Chrome profile but retains sign-in; and retains the booking-attempt journal. This is thorough transparency about side effects and what is preserved.

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 two sentences, front-loaded with the primary action. It wastes no words and efficiently communicates the core behavior and the key nuance about Chrome sign-in.

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 tool, the description is complete. It covers what is cleared, what is retained, and the Chrome profile behavior, leaving no ambiguity about the tool's effect.

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, so the baseline is 4. The description adds no parameter semantics because none exist, which is appropriate.

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 verb 'Clear' with clear objects: MCP authentication, pending confirmations, selected offers. It also distinguishes itself from Chrome sign-out, clarifying its exact scope, which differentiates it from sibling tools like login, recover_session, and status.

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?

It provides guidance on when to use this tool by clarifying that it clears MCP auth but not Chrome sign-in, explicitly directing users to 'sign out in Chrome separately.' This implies the tool is for MCP-level logout, not browser logout. It doesn't mention explicit alternatives but gives clear contextual instructions.

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