Attach to running Chrome

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

With no annotations, the description provides important behavioral details about the two modes (adopting logged-in session vs fresh isolated context) and mentions the return value (session id). It does not disclose safety or side effects, but the attach action is inherently non-destructive.

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 concise and front-loaded, using two sentences to convey the purpose, mode options, and return value without extraneous information. Every sentence adds value.

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 the tool's simplicity (2 optional parameters, no output schema), the description covers the essential context: the prerequisite, mode semantics, and the returned session id. The cdpEndpoint parameter is not explained, but its default value and commonality reduce the gap.

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 description explains the 'mode' parameter with explicit meanings for each enum value, but does not describe the 'cdpEndpoint' parameter beyond its default value. Since schema coverage is 0%, the description partially compensates by clarifying one of two parameters.

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 attaches to an existing Chrome instance with a specific prerequisite (--remote-debugging-port), and the verb 'attach' combined with the resource 'Chrome' makes the purpose distinct from sibling tools like browser_new_session.

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 explains when to use the tool (Chrome already running with debugging port) and describes mode options (default vs isolated), but does not explicitly state when not to use it or provide alternative tools. However, the context implies the usage boundary.

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