send_cdp_command

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

Covers side effects (depends on command, may modify page state), auth requirements (local-only restrictions), and return type, despite no annotations. Slight deduction for not specifying potential errors or rate limits.

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?

Every sentence earns its place, with clear sections for purpose, side effects, auth, prerequisites, return, and usage guidance. Front-loaded with purpose.

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 experimental nature and many siblings, the description covers purpose, when-to-use, side effects, auth, prerequisites, and return. Lacks error handling examples but schema compensates.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds minimal extra beyond schema, but constraints and interactions are mentioned for method parameter.

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?

Description clearly states the tool sends raw CDP commands for advanced cases not covered by specialized tools, distinguishing it from siblings.

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?

Explicitly says use only when specialized tools inadequate, lists alternatives (navigate, click_element, evaluate_js), and mentions prerequisites like CDP knowledge and active Chrome connection.

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