Connect to Google Flow

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

The description discloses behaviors beyond the annotations: it may launch Chrome if needed, opens a tab owned by the server, and can perform a one-time sign-in. These side effects align with the readOnlyHint=false and idempotentHint=true annotations and add meaningful operational context.

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?

Three sentences, no filler. The primary action is front-loaded, the purpose is stated, and the conditional login behavior is included without redundant 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?

For a single optional parameter with a full output schema, the description covers what the tool does, when to use it, and key side effects. Nothing needed for correct invocation is missing.

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%, so open_url is already well documented in the schema as a URL to open instead of the Flow home page. The description adds no extra parameter semantics, but the baseline of 3 is appropriate because the schema carries the full burden.

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 action: attach to the dedicated Chrome instance, open a server-owned tab, and load Google Flow. It also clarifies the tool's role as a warm-up and login check, distinguishing it from on-demand sibling tools.

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 explicitly says this is mainly a warm-up and login check while other tools connect on demand, giving clear usage context. It also provides the conditional action for logged_in being false, but it does not name specific sibling alternatives or explicitly state when not to use it.

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