browser_connect

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

The description discloses the ordering prerequisite but omits other behavioral traits such as side effects, error conditions, connection lifecycle, or cleanup requirements. Since no annotations are provided, the description carries the full burden, which is only partially met.

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, front-loaded sentence with no redundant text. Every word contributes to purpose and usage.

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 one-parameter connect tool with no output schema, the description covers purpose and a key prerequisite. It lacks explicit information about return values or post-connect behavior, but sibling tools like browser_navigate suggest the next steps, keeping this adequate.

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 schema already provides 100% coverage for the single parameter, describing the WebSocket endpoint and its source. The description adds no new parameter-specific meaning beyond the stated prerequisite, which is not directly about the parameter's format or usage.

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 identifies a specific action ('Connect') and resource ('running Octo Browser profile via CDP'), clearly distinguishing it from sibling tools like browser_disconnect and octo_start_profile.

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 states a prerequisite: 'Must be called after octo_start_profile.' This provides clear contextual guidance, though it does not mention alternatives or when not to use.

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