Clear DOM mutation, layout shift, or long task telemetry buffers from memory for active pages and observers, optionally by category.
Clear in-memory DOM mutations, layout shifts, or long tasks telemetry buffer across active page and observer.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Telemetry categories to clear: "all", "mutations", "layout-shifts", "long-tasks" (default: "all") | all |
Changes observed during successful MCP inspections.
v0.17.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that the buffer is in-memory and that clearing spans the active page and observer, which is real behavioral context. However, it does not say whether observation continues after the clear, whether the data is unrecoverable, or whether the observer must be re-armed.
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 front-loaded sentence with no filler. The noun phrase 'DOM mutations, layout shifts, or long tasks telemetry buffer' is slightly stacked and reads awkwardly, but nothing is wasted.
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 one-parameter, no-output-schema utility, the description covers the essentials. It leaves open the post-clear behavior of the observer and gives no routing guidance among the several sibling clear tools, which are the main 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?
Schema coverage is 100% with the enum and default fully documented in the schema, so the baseline of 3 applies. The description names three of the four categories but adds no syntax or semantic nuance beyond what the schema already states.
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?
Names a specific verb ('Clear') and resource ('DOM mutations, layout shifts, or long tasks telemetry buffer'), so the agent knows exactly what gets wiped. It is not differentiated from the many sibling 'clear' tools (vibeside_telemetry_clear, vibeside_hmr_clear, vibeside_clear_media_telemetry), so it falls short of a 5.
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?
Usage is only implied: the tool resets a telemetry buffer that siblings like vibeside_observe_dom_mutations and vibeside_observe_layout_shifts populate. There is no statement of when to clear versus when not to, and no comparison to the other telemetry-clearing siblings an agent must choose between.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.