Manage Fetch interception

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

With no annotations, the description carries the full burden. It discloses a critical behavioral fact: 'Paused requests remain blocked until handled or interception is disabled.' But it omits other important aspects such as session prerequisites, lifecycle, or cleanup, limiting 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?

The description is two sentences with no fluff. The first sentence enumerates all possible actions, and the second provides a crucial caveat. Every word adds value.

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 tool with 15 parameters, no output schema, and no annotations, this description is insufficient. It provides the action scope and one warning, but fails to explain how actions interact, what inputs are needed, or what responses look like.

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%, and the description does not explain any parameter semantics. The action list vaguely relates to the 'action' parameter, but the many other parameters (patterns, requestId, headers, etc.) are completely unexplained, making the tool very difficult to invoke correctly.

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 clearly states the tool manages CDP Fetch interception with a specific list of verbs (enable, poll, continue, fail, fulfill, list, disable) and the resource 'explicit CDP Fetch interception'. This distinguishes it from higher-level network tools like browser_network_start/poll/stop.

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 implies usage by identifying it as 'explicit CDP Fetch interception' and warns about paused requests remaining blocked. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria, so usage guidance is only implicit.

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