flow_browser_check_session

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

No annotations are provided, so the description carries the full burden; it does disclose the key non-destructive trait that the current page is not navigated away from. It does not disclose what happens on an invalid or expired session (error vs. boolean result), nor any authentication prerequisites for making the check itself.

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?

Two short sentences, front-loaded with the purpose and followed by the one behavioral detail that matters. Nothing is redundant or padded.

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 no annotations and no output schema, the description is the only source of truth about the result, yet 'returns the session state' is vague about shape (boolean, status enum, or object with expiry). For a zero-parameter boolean-style check this is workable but leaves the agent guessing what a return value actually looks like.

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 there is no parameter semantics to clarify; the baseline of 4 applies. The description does not waste words re-explaining 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 ('check') and a specific resource ('Google browser session') with the exact condition being tested (valid and active). It is clearly distinguishable from siblings like flow_browser_login or flow_browser_action, though it does not name any sibling to route against explicitly.

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 clause 'without navigating away from the current page' implies a pre-flight check that is safe to call before other browser operations, which is useful context. However, it never states when to call this versus flow_browser_login (e.g., 'call this before flow_browser_action to decide whether login is needed').

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