flow_connect

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

With no annotations, the description must carry the behavioral disclosure burden. It reveals the connection target and default port, but does not say whether this launches a browser, mutates state, is idempotent, or is required before other operations. This is a meaningful gap for a stateful connect tool.

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, efficient sentence that conveys the action, target, and default port with no filler. Every piece of information serves the agent's selection and invocation decision.

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 simple tool with one optional parameter and no output schema, the description covers the core action and default. However, it lacks behavioral side effects, prerequisites, and any indication of what a successful connection yields, so an agent has only partial context for correct invocation.

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?

Schema description coverage is 100% and the single parameter 'headless' is fully described with its default and anti-bot rationale. The description itself does not add parameter information, but the baseline of 3 applies because the schema already documents the parameter well.

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 states a specific verb ('Establishes connection') and a specific resource ('Google Flow Chrome instance on CDP port'), which clearly distinguishes it from sibling tools like flow_disconnect and flow_status. The default port value adds precision.

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?

No guidance is given about when this tool should be used, whether it must precede the other flow_* tools, or when a sibling like flow_status might be more appropriate. The purpose is implied by the name and description, but explicit usage context is absent.

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