browser_cdp_command

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'raw' which hints at low-level power, but does not disclose potential side effects, safety risks, or required permissions. This is a significant gap for a tool that can execute arbitrary CDP commands.

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 concise sentence with no wasted words. It is front-loaded and immediately communicates the tool's core function, though it lacks elaborative detail that would come at the cost of conciseness.

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 that executes raw CDP commands, the description is under-specified. It lacks information about the nature of CDP, safety considerations, or how the output should be interpreted. While the output schema exists, the description still needs to convey the operational context, which it fails to do.

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?

The input schema provides 100% coverage with all three parameters (slot, method, params) having descriptions. The description adds no additional meaning beyond the schema, matching the baseline for full schema coverage.

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 'Execute a raw CDP command' clearly states the tool's action and object, using the specific verb 'execute' and the resource 'raw CDP command'. It is distinct from sibling tools by being a low-level interface, though it does not explicitly differentiate from alternative higher-level browser tools.

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 the specialized sibling tools such as browser_use_tor or browser_network_intercept. The one-line description provides no context about appropriate use cases, prerequisites, or exclusions.

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