runtime_evaluate

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that JavaScript will be executed, but it does not warn about arbitrary side effects, page mutation, network activity, prerequisite attachment, or what happens to returned values. The behavior beyond 'runs code' is undisclosed.

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 one tight sentence with no filler. The verb, target, and protocol are all front-loaded, and every word contributes to identifying the operation.

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 potentially side-effectful execution tool with no annotations and no output schema, this description is too thin. It omits prerequisites, safety considerations, return behavior, and optional parameter semantics, leaving an agent to infer critical details from CDP knowledge alone.

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 for parameter meaning. It only vaguely maps to 'expression' and 'tab' through its wording; it says nothing about awaitPromise or returnByValue, leaving the optional parameters underspecified.

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 uses a specific verb ('Evaluate') with a clear resource ('JavaScript in the inspected tab') and names the underlying CDP method, making the tool's purpose immediately obvious and distinct from sibling tools like console_read or network_read.

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?

No guidance is given about when to use this tool versus alternatives, when not to use it, or whether it requires a prior step such as devtools_attach. The intended use is implied by the name and description but never explicitly stated.

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