electron_connect

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

No annotations are present, so the description must carry the full behavioral burden. It mentions that the app must be 'running' and that it connects to both ports, but it doesn't disclose potential side effects, whether it requires configuration, or what happens on failure. It lacks detail on connection lifecycle.

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 sentence that directly states the tool's purpose without wasted words. It is appropriately front-loaded.

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 tool that establishes a connection, the description is sparse. It doesn't mention what the connection is used for, how it interacts with later commands, or what output to expect. Given the complex sibling ecosystem (v8, chrome, connection managers), more context is needed.

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 has 100% coverage with clear parameter descriptions, and the tool description adds no additional semantic information beyond what the schema provides. Baseline of 3 is appropriate.

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 verb 'Connect' and identifies the resource as a running Electron app on both CDP and V8 Inspector ports. This distinguishes it from sibling tools like v8_connect (which only handles V8) and chrome (which handles Chrome).

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 provides no guidance on when to use this tool versus alternatives such as v8_connect or chrome. It doesn't mention that it should be used after electron_setup or that it combines both CDP and V8 connections into one step.

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