activate_cdp_mode

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

No annotations are provided, so the description carries the full burden. It discloses a side effect: switching session mode affects subsequent actions. It also notes the prerequisite 'uc=True'. However, it doesn't disclose potential side effects like whether the session state is altered irreversibly, or whether it conflicts with other operations. Since it's a state-changing operation, more disclosure would be expected.

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 two sentences, which is concise. It front-loads the primary action and then provides additional context. Every sentence adds relevant information without fluff.

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?

The tool has an output schema (though not shown in the input), and the description is adequate for a simple parameter. However, given it's a session state change, the description could be more complete about what changes and how it affects subsequent actions. The prerequisite 'uc=True' is a critical detail, but other caveats like session reset or limitations are not mentioned. Overall, it's minimally viable but has gaps.

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?

The schema has 0% coverage for the parameter, but the description mentions 'optionally navigating to a URL', which explains the purpose of the 'url' parameter. Since there is only one parameter and the description covers its purpose, it adds some value beyond the bare schema. However, it doesn't detail the format or expectations for the URL, even though the schema is minimal.

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 tool's purpose: it switches the current session into Pure CDP Mode and optionally navigates to a URL. The verb 'switch' and resource 'session into Pure CDP Mode' are specific. It also mentions 'CDP-only capabilities' which distinguishes it from general navigation tools like 'navigate'.

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?

The description gives context that this mode applies to subsequent actions and mentions a prerequisite: 'Requires uc=True.' However, it doesn't explicitly state when to use this over alternatives or when not to use it. The context of 'more thorough stealth' implies a use case, but there's no direct comparison with siblings like 'navigate'.

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