flow_connect

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

No annotations are provided, so the description carries the transparency burden. It discloses the exact steps (launch Chrome, connect CDP, navigate, verify) and a warning about headless mode, which is useful. However, it omits side effects (e.g., opening a visible browser window) and does not clarify what happens if already connected or how 'verify account' behaves on failure.

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 concise sentence that front-loads the main action and includes all key steps without wasted words. It is efficient and easy to parse, earning a perfect score.

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 setup/connection tool with no output schema and no annotations, the description covers the main workflow and warns about headless usage. It is mostly complete, though it could mention idempotency or error handling, but those are not critical for a basic connect operation.

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 provides full descriptions for both parameters (headless and open_flow) with 100% coverage, so the baseline is 3. The tool description adds context about the overall workflow but does not add new meaning to the individual parameters beyond what the schema already states.

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 specifies a multi-step purpose: launch Chrome with the configured Google profile, connect CDP, navigate to Google Flow, and verify account. It uses a specific verb sequence and explicitly names the resource (Google Flow), and it is easily distinguished from siblings 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 is the connection/setup tool and provides a clear usage guideline for the headless parameter ('not recommended, Google Flow needs visible browser'). However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites like being disconnected first.

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