Disable console collection

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

Beyond the idempotentHint annotation, the description explains the underlying mechanism (turns off CDP Runtime domain), the anti-bot detection benefit (quieter, harder-to-detect default), and the key side effect that 'Messages already collected stay readable; only new ones stop arriving.' This is exactly the kind of behavioral context that helps an agent predict outcomes.

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 three tight sentences, front-loaded with the main action, then providing rationale and a side effect. Every sentence earns its place—no fluff, no redundant restating of the title. It is a model of concise yet informative writing.

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 zero-parameter tool with an output schema, the description provides all necessary context: what it does, when to use it, why it matters, and what happens to collected data. It is fully complete for the tool's complexity and leaves no major behavioral questions unanswered.

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?

There are zero parameters, so the baseline is 4. The description adds no parameter-level details because none are needed. It doesn't need to compensate for any schema gaps since the schema is empty and coverage is 100%.

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 opens with a specific verb+resource: 'Stop capturing console output on the current page.' This clearly distinguishes it from sibling tools like enable_console_collection and list_console_messages. The purpose is unambiguous and action-oriented.

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 provides clear context for when to use: 'once you are finished debugging and the page still has anti-bot checks ahead of it.' This implies when it's appropriate, but it doesn't explicitly mention alternatives or exclusionary cases (e.g., when you still need new messages). Still, the context is strong enough to guide the agent.

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