Raw DevTools Protocol command

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

Annotations already mark it as non-read-only and open-world, and the description adds useful behavior beyond that: automatic routing through the full DevTools channel for domains unavailable to extensions, and the safeguard that disabling domains other tools rely on is ignored. It does not cover error behavior or permission requirements, but the added routing context is valuable.

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 definition is front-loaded with the core action and is only three sentences long. Each sentence adds relevant information, though the routing and domain-disabling details are slightly dense.

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 raw CDP command tool with no output schema, the description explains that it returns the raw result and clarifies routing and target behavior. It is largely complete given the rich schema and annotations, with only minor gaps around error handling and explicit alternative selection.

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 all six parameters are already documented. The description reinforces target selection for tab, iframe via frame ref, and child session id, but adds little beyond the schema's own parameter descriptions.

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 states a clear verb and resource: it sends any Chrome DevTools Protocol command to a tab, iframe, or child session and returns the raw result. This distinguishes it as a raw CDP escape hatch, though it does not explicitly contrast itself with sibling tools such as cdp_events or evaluate.

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?

Usage is implied by “any Chrome DevTools Protocol command,” suggesting it is for arbitrary or low-level CDP calls rather than higher-level helpers. However, it does not explicitly say when to prefer this over sibling tools or when not to use it.

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