Check Session Status

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds useful behavioral context beyond annotations: it may launch or reuse a browser, verifies landing on a signed-in /sales page, and returns the profile directory and headless setting. No contradiction with 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?

Description is compact and front-loaded. The core purpose appears in the first sentence, usage guidance in the second, and a clear 'Returns:' block for the result structure. Every sentence earns its place.

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 tool with an output schema, this description covers purpose, usage timing, behavioral side effects, and return summary. Nothing essential is missing for an agent to decide when to call and interpret the result.

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 empty schema properties, so the semantic baseline is high. The description does not need to explain parameters; its return-value summary compensates for the lack of param-related guidance.

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 resource: checking whether the browser profile has a live Sales Navigator session. The description distinguishes this from siblings like outreach_status and pipeline_status by focusing on session/sign-in state rather than campaign or outreach state.

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?

Explicitly says 'Use this first when searches fail' and mentions the decision outcome: whether to run `--login` again. This gives clear when-to-use guidance and implicitly differentiates it from search-oriented sibling tools.

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