send_cdp_command

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

With no annotations, the description fully discloses behavioral traits: side effects ('may modify page state, DOM, or trigger navigation'), auth restrictions (local-only for Page.navigate), and the experimental nature. It clearly states the raw return format. This is exactly what a high-risk tool needs.

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 dense but every sentence earns its place: experimental warning, purpose, side effects, auth, prerequisites, return type, and usage guidance. Front-loaded with the 'EXPERIMENTAL' warning and purpose. No filler or repetition.

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?

Given the tool's complexity (raw CDP, safety, auth, prerequisites) and lack of output schema, the description covers all necessary context: what it does, when to avoid it, side effects, auth, prerequisites, and return format. Nothing an agent needs to safely and correctly invoke it is missing.

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 coverage is 100% for all 4 parameters, so the baseline is 3. The description reinforces constraints (e.g., 'Page.navigate URLs subject to local-only restrictions') but does not add meaning beyond what the schema already provides. It mentions the JSON format for params, but the schema says the same. No extra semantic value.

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 verb 'sends' with the resource 'raw Chrome DevTools Protocol (CDP) commands' and explicitly frames it as 'for advanced use cases not covered by specialized tools.' It distinguishes itself from siblings by naming alternatives (navigate, click_element, evaluate_js) and stating when it should not be used.

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?

Provides explicit guidance: 'Use this only when specialized tools inadequate' and directly lists alternative tools. It also states prerequisites (knowledge of CDP protocol, active Chrome connection) and auth caveats (local-only restrictions for Page.navigate). This is comprehensive routing advice.

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