Clear all stored browser console messages to reset captured logs and ensure AI debugging sessions start with a clean console state.
Clear all stored console messages.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Clear all' implies a destructive, bulk mutation, but the description never states whether the operation is irreversible, what happens to concurrent captures, or what is returned (count cleared, nothing, etc.) — significant gaps for a destructive 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?
A single tight sentence with the scope ('all stored') front-loaded and no filler. It is efficient, though arguably under-specified rather than optimally concise given the destructive nature of the operation.
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 destructive, non-annotated, no-output-schema tool, the description omits irreversibility, side effects, and return behavior. An agent cannot confidently reason about the consequences of calling it from this text alone.
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 tool takes zero parameters, so there is nothing for the description to document and the schema is trivially complete (100% coverage). Baseline 4 applies for a parameterless tool.
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?
States a specific verb (Clear) and resource (console messages) with a scope qualifier (all stored). It is unambiguous and distinguishable from its getter siblings (get_console_messages, get_console_errors, get_console_stats), though the description never explicitly contrasts itself with them.
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?
No guidance on when to use this tool versus the sibling read tools, no mention of prerequisites, and no note on whether it should be called before/after inspecting messages. The purpose is inferable but usage context is entirely absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.