LinkedIn Session Status

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds the valuable caveat that only non-secret state is returned, specifying what is not exposed. It also scopes the state to the configured account, providing context beyond the 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, front-loaded sentence: 'Return non-secret browser-session state for the configured account.' It contains no redundant words and is immediately comprehensible.

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?

This is a simple read-only status tool with no parameters and an output schema. The description and annotations fully cover its behavior, purpose, and safety profile, leaving no significant gaps.

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?

This tool has zero parameters, so the description doesn't need to elaborate on parameter semantics. The baseline for no-parameter tools is 4, and the description provides sufficient clarity given the schema is already complete.

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 the tool returns non-secret browser-session state for the configured account, using a specific verb (Return) and resource (browser-session state). It distinguishes from sibling linkedin.server.status by focusing on account session rather than server status.

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 for checking the account session, but it doesn't explicitly state when to use it or provide alternatives. There is no exclusion of similar tools like linkedin.server.status, so usage context is implied rather than stated.

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