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

Annotations already declare readOnly/openWorld=false/destructive=false, so the safety profile is covered; the description adds the operational facts the annotations cannot: the link runs in a server-side browser inside the account's own profile and proxy, the full session is auto-captured after the human logs in, a human must complete it, and the agent must never request the password. That is exactly the extra behavioral context this dimension rewards.

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?

Front-loaded with the purpose in sentence one, then progressively adds rationale and constraints. It is fairly long and slightly repetitive (the cookie/password advice is restated twice), but every sentence carries real decision-relevant information, so the density justifies the length.

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?

Covers what the tool returns conceptually (a link), what happens after it is opened, who must act (a human), and what the agent must not do. With no output schema, this is complete enough for an agent to invoke and follow up correctly.

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 description coverage is 100% and both parameters (sessionId, sessionLabel) are documented inline, so the baseline is 3. The description never mentions either parameter or explains the id-vs-label choice, so it adds no meaning beyond the schema.

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?

Opens with a specific verb and resource ('Return the dashboard link that opens a REAL LinkedIn login for an account') and immediately qualifies it with the operating environment (server-side browser, account's own profile, its own proxy). An agent can distinguish this from sibling tools like li_session_status or li_verify_account without opening any schema.

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?

Explicitly names the triggering conditions — account blocked, expired cookies, or first-time connection — and rules out the alternative approach ('strictly better than asking the user for cookies', with a concrete rationale about li_at/JSESSIONID). It does not name a specific sibling tool to prefer or avoid, so it stops just short of a 5.

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