vibeside_observe_dom_mutations

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

No annotations are provided, so the description carries the full behavioral burden. 'Observe' implies a read/telemetry operation, but the description says nothing about buffer persistence, whether observation is continuous or point-in-time, how results are returned, or what happens when thresholds trip beyond the bare param names.

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 three well-ordered clauses, zero filler, and the primary action stated first. It is efficient, though the dense triple-clause structure is the only thing carrying the whole definition.

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?

With 7 parameters, no annotations, and no output schema, the definition should explain how to interpret the storm/critical results and the interaction between clearAfterRead and the sibling clear tool. It covers the what but leaves the how-to-interpret and lifecycle 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 description coverage is 100%, so every parameter (limit, windowSec, filterType, clearAfterRead, filterSelector, stormThreshold, criticalThreshold) is already documented in the schema. The description adds no syntax, format, or interaction detail beyond that baseline.

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 names a specific verb and resource ('Observe live DOM mutations') and adds two concrete capabilities (sliding-window rate evaluation, re-render storm hotspot detection). It is clear what the tool does, but it never distinguishes itself from close siblings like vibeside_dom_snapshot or vibeside_clear_dom_telemetry.

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?

There is no statement of when to use this tool versus alternatives such as vibeside_dom_snapshot, vibeside_observe_layout_shifts, or vibeside_clear_dom_telemetry. No prerequisites, no exclusions, no context for choosing this over a one-shot DOM snapshot.

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