logout

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

With no annotations, the description carries the full behavioral burdenheb and does well by clearly disclosing that it removes all stored session credentials, cookies, and local profile caches. It accurately conveys the destructive, session-ending nature of the operation without relying on the schema or annotations.

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 a single, efficiently written sentence that front-loads the action and lists the affected resources without any filler or redundancy. Every word contributes to the agent's understanding of the tool's behavior.

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 with an output schema, the description fully covers what the tool does and what it affects. No additional behavioral context is needed for an agent to decide whether to invoke it, and the output schema handles return-value semantics.

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 parametersplay. The empty schema is fully self-explanatory, and the description adds no parameter information because none is needed. The baseline of 4 for zero-parameter tools applies.

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 ('Clear') and identifies the exact resources affected: stored LinkedIn session credentials, cookies, and local profile caches. This makes the tool's purpose unmistakable and distinguishes it from session-management siblings like check_login_status, start_login, and refresh_session.

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 description does not explicitly state when to use this tool versus alternatives, nor does it mention any preconditions or side effects beyond clearing credentials. The use case is inferable from the name and wording, but the tool provides no direct guidance about session lifecycle or when logout is appropriate.

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