flow_connect

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

The description discloses that headless mode is not recommended and lists the sequence of actions (launch, connect, navigate, verify). However, it does not mention side effects like opening a visible browser window or potential need for user authentication, which would enhance transparency.

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, well-structured sentence that efficiently conveys the tool's purpose and key actions without extraneous detail.

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?

Given no output schema, the description should specify what 'verify account' returns (e.g., success, error, connection status). The lack of information about output or side effects makes it incomplete for an AI agent to use correctly.

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 input schema already provides 100% coverage with descriptions for both parameters. The description adds value by clarifying the 'headless' default and the profile usage, but does not significantly extend beyond the 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?

The description clearly states the tool's purpose with specific actions: launching Chrome, connecting CDP, navigating to Google Flow, and verifying account. This effectively distinguishes it from sibling tools like flow_disconnect or flow_status.

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 implies this tool is for initial setup before using other flow tools, but provides no explicit guidance on when to use it versus alternatives, nor when not to use it. A mention of prerequisites or ordering would improve clarity.

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