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

With no annotations, the description usefully discloses that authentication relies on a pasted session cookie and that no redirect is involved. It does not explain what happens after connection, whether credentials are stored, failure modes, or security implications, so the behavioral picture is only partially covered.

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 short and front-loads the main purpose before the relevant cookie-acquisition steps. The redundant heading 'Connect Linkedin Li At' and boilerplate 200 response line slightly reduce efficiency, but the content is easy to scan.

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 two-parameter connection tool with no annotations, no output schema, and 0% schema coverage, the description adequately explains the required secret. It remains incomplete because it omits the country parameter and post-connection behavior, which an agent would need to invoke the tool confidently.

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 0%, so the description must compensate. It provides detailed guidance on obtaining and copying the required li_at value, but it never mentions the optional country parameter or its purpose, leaving one of two parameters undocumented.

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 a specific action and resource: connect LinkedIn by supplying the li_at session cookie. It distinguishes the method from OAuth and redirect-based flows, though it does not explicitly name or contrast the other connect_linkedin_* sibling 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?

It gives the necessary precondition—having a li_at cookie—and notes that this is lower friction than OAuth with no redirect, which implies when the method is appropriate. However, it never explicitly says when to use this instead of connect_linkedin_credentials, connect_linkedin_url, or connect_linkedin_checkpoint_mcp.

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