cdp_send

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

No annotations were provided, so the description carries the full behavioral burden. It does disclose meaningful behavioral traits: CDP is scoped to the tab's current origin, attaching shows the 'started debugging' bar, and it requires full CDP access enabled. However, it doesn't describe what the response looks like, failure modes, or the relationship between session_id vs target_id and target_id. Decent disclosure but not exhaustive for a raw power tool.

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 well-structured paragraph front-loaded with the core purpose, followed by practical usage notes. Every sentence earns its place, but it's slightly dense—four sentences packed with guidance. Still appropriately sized for a complex low-level tool; no waste.

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 no annotations and no output schema, the description covers a lot: prerequisites, origin scoping, event observation pattern, and higher-level alternatives. For a complex 6-parameter tool with nested objects and no output schema, this is reasonably complete, though it could clarify response/return semantics and error behavior. The description compensates well for the missing structured metadata.

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%, so the baseline is 3. The description adds value by explaining the tab_id targeting mechanism and how cdp_events/cursor interplay works with sending commands, which goes beyond the schema's bare descriptions. It also explains the session_id/target_id distinction contextually with 'attached child target.' Though the high-level event workflow is described, it doesn't elaborate on params semantics beyond what the schema provides.

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 is specific: it sends a raw CDP command to the active tab or specified tab via the browser's cdp capability, explicitly scoped for developer/debugging use. It clearly distinguishes this low-level tool from the 'higher-level tools for ordinary automation.' The verb+resource+scope are all precise.

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?

Excellent guidance: tells users to navigate to the intended http(s) page first, explains origin scoping, warns about the 'started debugging' bar, explicitly says to prefer higher-level tools for ordinary automation, and describes the cdp_events cursor workflow for observing events. Also notes the full_cdp_access_enabled prerequisite. This is thorough when-to-use/when-not-to-use guidance.

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