reconnect_devtools

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

With no annotations, the description carries the behavioral burden and does disclose the stateful reuse/replacement behavior. However, it omits important consequences such as the effect on an existing connection, what happens if no previous successful request exists, and the behavior of timeoutMs/healthCheck.

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?

A single sentence efficiently packs two usage branches with no filler, and the default no-argument behavior is front-loaded. Every word contributes meaning.

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?

The tool has a complex discriminated-union target plus timeoutMs and healthCheck, yet the description covers only the target/no-target distinction. It omits target kind semantics, parameter behavior, failure conditions, and any guidance about the output, leaving the schema to do nearly all of the explanatory work.

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 0%, so the description must compensate, but it only mentions target as a trigger for a new request. It does not explain timeoutMs, healthCheck, or the four target variants (project, wsEndpoint, browserUrl, discover) that the schema defines.

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, non-tautological behavior: with no parameters it reuses the last successful request, and with target it replaces it with a new request. However, it never explicitly names the DevTools reconnection outcome, and it does not differentiate this tool from connect_devtools or disconnect_devtools.

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?

It provides clear branch conditions for when to omit parameters versus when to pass target. But it does not advise when to choose reconnect_devtools over the sibling connection tools, and it gives no exclusion cases.

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