Enable console collection

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

Beyond the annotations (idempotentHint=true, readOnlyHint=false), the description discloses significant behavioral context: it enables the CDP Runtime domain, explains why it is opt-in (anti-bot scripts probe for it), and notes that it applies per page. This adds value beyond what annotations provide and helps the agent understand side effects and stealth implications.

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 compact and well-structured: the first sentence gives the core purpose, followed by short, informative sentences about prerequisites, rationale for opt-in, and per-page behavior. Every sentence earns its place; no filler or redundancy.

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?

For a tool with no parameters and an output schema, the description covers all necessary context: when to call it, its relationship to related tools, why it is opt-in, and per-page behavior. The output schema handles return values, so no additional return explanation is needed.

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 input schema has zero parameters, so the description cannot add parameter-specific meaning. Per the baseline rule for 0 params, a score of 4 is appropriate. The description focuses on behavior and prerequisites, which is all that is needed here.

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 action and resource: 'Start capturing console output on the current page.' This is a specific verb+resource construction that immediately distinguishes it from sibling tools like list_console_messages, get_console_message, and disable_console_collection.

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 explicit usage guidance: 'Call this before list_console_messages or get_console_message' and explains the alternative (network capture is always on). It also specifies when not to use it (when stealth matters) and mentions the companion disable_console_collection for cleanup. Additionally, it clarifies the per-page scope.

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