Sign in to LinkedIn

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

With no annotations, the description carries the behavioral burden, and it discloses key traits: it opens a browser window, requires the user to sign in and close the window, and persists/restores the session. It does not cover failure modes or what the tool returns, but the main side effects are transparent.

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?

Two short sentences deliver the action, the user's required step, and the persistence behavior with no filler. The key 'one-time' instruction and close-window step are front-loaded.

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 interactive login, the description is complete enough: it tells what the user must do, what the tool does, and what happens to the session afterward. No return format is necessary for correct invocation.

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 100% schema description coverage, so there is nothing for the description to add to parameter semantics. Baseline 4 applies because no parameter guidance is needed.

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 opens with a specific action—'Opens a browser window for a one-time sign-in'—and the title names the resource (LinkedIn). The 'one-time' wording also helps distinguish this interactive login from session-status or other account tools.

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 gives clear context: this is a one-time, interactive setup whose session persists across restarts, so an agent knows not to call it repeatedly. It does not explicitly list alternatives or say 'use session_status if already signed in,' so it lacks explicit when-not guidance.

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