jev_chrome_guard

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

With no annotations, the description carries the full behavioral burden. It hints at a security gate ('Layer-0 DLP/SSRF pre-screening') and 'zero-popup' launch behavior, but never says what happens when screening blocks a request, whether errors are returned or calls silently fail, or that some CDP methods (DOM.setFileInputFiles, Page.navigate) mutate browser state destructively. Undefined jargon like 'Layer-0' adds no actionable transparency.

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?

It is a single short sentence with no filler, which is good, but it is packed with stacked compound jargon ('Layer-0 DLP/SSRF', 'M144+', 'DevToolsActivePort') and leads with an adjective rather than the primary action. Dense does not equal front-loaded; the core action is never stated.

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?

This is a complex tool with a nested free-form 'params' object, a CDP method dispatcher, security gating, and no output schema or annotations. The description leaves open what the tool returns (a port path, a screening verdict, a CDP result?), how blocked calls surface, and what state changes are possible — significant gaps for an agent to call it correctly.

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 100% and each of the four parameters is documented in the schema itself, so the baseline is 3. The description adds nothing about parameters — notably it never explains the relationship between 'params', 'method', and the pre-screening step, nor what 'target_url' is actually screened for.

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 names concrete concepts (DevToolsActivePort discovery, DLP/SSRF pre-screening, CDP automation) that identify the resource area, but it is a noun phrase with no clear verb and never states that the tool actually dispatches the CDP call implied by the 'method' parameter. An agent cannot confidently tell whether this only discovers a port and screens a URL or also executes Runtime.evaluate/DOM.setFileInputFiles against the browser.

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 at all: nothing distinguishes this from siblings such as jev_guard, jev_route, or jev_autopilot, and no preconditions (a live Chrome instance, an authenticated session) are stated. The only implied context is 'live browser CDP automation', which is too thin to route between tools.

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