vibeside_clear_media_telemetry

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

With no annotations, the description carries the full burden. It does disclose one useful behavioral fact — events are buffered and live in memory — implying the clear is a memory-buffer reset rather than a persistent deletion. It does not say whether telemetry collection continues afterward, whether the clear is reversible, or whether permissions are needed.

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?

One front-loaded sentence with no filler, correctly sized for a single-parameter clear 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 simple clear tool with no output schema and full parameter coverage, the essentials are present, but the description omits the relationship to the observation tools (does clearing stop or reset vibeside_observe_media_events?) that an agent would need to sequence these calls correctly.

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% for the single optional selector parameter, so the schema already documents that omitting it clears everything. The description adds no format, matching, or scope detail beyond what the schema states; baseline 3 applies.

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 a well-scoped resource ("buffered HTML5 media telemetry events"), which distinguishes it from generic siblings like vibeside_telemetry_clear and vibeside_clear_dom_telemetry. It does not name those siblings explicitly, so an agent must infer the media-vs-DOM-vs-general split from the noun phrase alone.

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 when-to-use guidance, no prerequisite, and no mention of alternatives such as vibeside_observe_media_events (to observe) or vibeside_telemetry_get (to read before clearing). The only conditional phrasing, "or omit to clear all," describes a parameter default rather than a usage decision.

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