refresh_session

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

With no annotations, the description carries the burden of behavioral disclosure. It does convey that the tool performs a keep-alive and extends session validity, but it does not mention side effects, failure behavior, authentication requirements, or rate-limit implications. This adds some behavioral context but not rich detail.

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 sentence and front-loads the main action. The phrase 'sliding window keep-alive telemetry' is somewhat vague and could be trimmed, but overall the description is appropriately concise.

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 no-parameter tool with an output schema, the description is mostly sufficient to understand what the tool does. However, it lacks guidance on when to use it relative to session-related siblings and does not clarify the meaning or implications of 'sliding window keep-alive telemetry.'

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, so the schema already fully covers the parameter surface. The description has no need to explain parameter semantics, and the empty schema makes this a non-issue.

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 names a specific verb ('Test and extend') and resource ('active LinkedIn session validity'), which clearly distinguishes it from siblings like check_login_status, start_login, and logout. The phrase 'sliding window keep-alive telemetry' is somewhat jargon-heavy but does not obscure the core purpose.

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?

There is no explicit guidance on when to call this tool versus alternatives such as check_login_status or start_login. The description implies it is used to maintain session validity, but it does not state prerequisites, exclusions, or a preferred call order.

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