Manage debugger lifecycle

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action (enable/disable) without revealing side effects such as impact on existing breakpoints, session state, or reversibility. This is a significant gap for a tool that modifies a debugging domain.

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, front-loaded sentence with no redundant words. It is appropriately concise for a relatively simple toggle action.

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 lack of annotations, output schema, and parameter explanations, the description is minimally sufficient but incomplete. It omits details such as what happens if the session is invalid, whether enabling affects performance, and how it relates to other debugger lifecycle operations. The tool is simple, but more context would be needed for safe usage.

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 0%, and the description does not explain any of the three parameters. It fails to clarify the purpose of targetSessionId or how the action and sessionId map to the described behavior, leaving the agent to guess from the bare schema.

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 uses a specific verb ('Enable or disable') and a clear resource ('Debugger domain on an existing Raw CDP session'), making it distinct from sibling debugger tools like debugger_pause or browser_cdp_send. It answers what the tool does precisely.

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?

It clearly states the prerequisite of an existing Raw CDP session, implying use after attaching a session (e.g., via browser_cdp_attach). However, it does not explicitly mention alternatives or when not to use this tool, leaving the guidance slightly less explicit than ideal.

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