check_login_status

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verbs 'check' and 'inspect' imply a read-only operation with no side effects, which is useful, but the description does not mention what happens for an expired/invalid session or what identity fields are included. It is adequate but minimally detailed.

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 with no wasted words. It directly states the primary purpose and the additional identity inspection capability without redundancy.

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 zero-parameter, read-only status-checking tool with an output schema available, the description covers the essential behavior. It could be slightly more complete by explicitly noting that this is the tool to use for verifying the current session before performing authenticated actions, but the low complexity means nothing critical is missing.

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, and the schema coverage is 100% trivially. The description adds no parameter details because none are needed, and the baseline for a zero-parameter tool is appropriate.

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 checks LinkedIn authentication status and inspects the active user's identity details. It is specific about the action and resource, though it does not explicitly differentiate itself from the sibling get_my_profile, which could also involve retrieving user identity information.

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 provides no guidance on when to use this tool versus alternatives like start_login, logout, refresh_session, or get_my_profile. The intended context of 'call this to verify an authenticated session' is only implied by the tool name, not stated in the description.

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