browser_cdp_send

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

No annotations are provided, so the description carries the full burden. It communicates that commands are raw and includes a timeout, but does not disclose side effects, permission requirements, reversibility, error behavior, or that powerful commands like 'Fetch.enable' or 'Tracing.start' can alter browser state. It lacks the concrete behavioral context needed for a raw protocol passthrough.

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 a single front-loaded sentence with no wasted sentences, and the core capability is stated first. 'GOD MODE' is informal branding that adds little informational value, keeping it from a perfect score.

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 high-complexity universal tool with nested params, no output schema, and no annotations, the description is adequate but thin. It does not explain how to discover valid CDP methods, what happens on invalid commands, or what the response looks like, leaving significant gaps for an agent invoking raw protocol calls.

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%, so the schema already documents method, params, and timeout. The description adds examples of valid method values, but these overlap with the schema's own examples and do not clarify params structure or timeout tradeoffs beyond what is structured.

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 (Send) and resource (raw Chrome DevTools Protocol command) with explicit scope (any, directly with custom parameters). It distinguishes itself from siblings by positioning as a universal escape hatch, giving examples like 'DOM.getBoxModel' and 'Fetch.enable' that no other listed tool covers.

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 phrase 'UNIVERSAL RAW CDP (GOD MODE)' implies this is the fallback for arbitrary CDP commands not exposed by dedicated browser_* tools, but there is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. Usage is implied rather than stated.

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