Get Session Status

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

Goes well beyond readOnlyHint/openWorldHint by disclosing that no browser is opened, no setup or login occurs, no LinkedIn contact is made, and the browser idle timer is not refreshed. It also flags the important semantic caveat that stored files do not prove current authentication and that in shared-browser mode observations belong to the owner rather than a frontend running a login.

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, then layered caveats and the sibling-routing sentence. Every sentence carries information, though the idle-timer sentence is slightly awkwardly worded and the density of caveats makes it longer than strictly minimal.

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?

With an output schema present, return values need no explanation, and with no parameters there is nothing else to document. The description covers safety-adjacent semantics (auth proof, shared-browser ownership) plus the selection rule, leaving nothing an agent needs before calling it.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add. It does not waste space restating an empty 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?

States a specific verb and object: report local saved-session and serving-process state for diagnostics. It is immediately distinguishable from every sibling, which are all LinkedIn actions, and it explicitly disclaims LinkedIn interaction so the agent will not confuse it with a connectivity or auth check.

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?

Gives explicit when-to-use (requested diagnostics) and an explicit when-not-to-use: 'Use ordinary LinkedIn tools directly for their requested work rather than adding a status preflight.' That names the alternative behavior, which is the main mis-selection risk for a status tool in a browser-automation suite.

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