reconnect

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing: it does not say whether reconnecting drops the current session, loses page state, requires the browser to be in a failed state, or has any side effects. Two words cannot cover a session-level operation.

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?

Two words are technically concise but reflect under-specification rather than economy, the same failure mode as a bare "Process" description. Nothing is front-loaded because nothing meaningful is said.

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?

With no parameters, no output schema, and no annotations, the description is the only source of behavioral information, and it omits when to call it, what state change occurs, and what the caller should expect afterward. It is insufficient for a lifecycle tool sitting beside health_check and reload.

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 tool takes zero parameters and the schema is empty, so there are no parameter semantics for the description to clarify. The baseline of 4 applies since the schema already fully specifies the absence of inputs.

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?

"Reconnect browser" essentially restates the tool name with its resource and adds no differentiating detail. An agent cannot tell how this differs from siblings like reload, navigate, or health_check, which is the key ambiguity for a browser-session tool.

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?

There is no when-to-use guidance, no mention of the condition that warrants reconnecting (e.g., a dropped session or stale connection), and no reference to alternatives such as reload or health_check. Usage is only faintly implied by the verb.

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