linkedin_logout

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

No annotations are provided, so the description carries full burden. It discloses the two effects (sign out + close context), but doesn't clarify whether this is destructive to any saved state, whether session data is preserved for future logins, or what happens to cookies/credentials. For a session-terminating action, this is a meaningful gap.

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?

Single sentence, two clear actions, zero waste. Efficient and appropriately sized for what is a simple stateless operation.

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 simple logout with 0 parameters and no output schema, the description conveys the core behavior. However, it doesn't address state implications (e.g., whether the browser context closing also affects other open tabs or sessions) or confirm what success looks like. Given the tool's simplicity, this is adequate but could note side-effects.

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 0 parameters, so there's nothing to document. The baseline of 4 for zero-parameter tools is appropriate; the description adequately explains the action without needing parameter detail.

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 verb+resource: 'Sign out of LinkedIn... and close the browser context.' It distinguishes from siblings like linkedin_login and close_browser by combining logout with context closure. However, it doesn't explicitly distinguish from close_browser alone, though the combined action differentiates it.

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 implies this is used when ending a LinkedIn session, but provides no explicit when-to-use versus alternatives like close_browser. No exclusions or guidance on when not to use it.

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