vibeside_telemetry_clear

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 for a destructive operation. It says 'clear all' but never states whether the wipe is irreversible, whether it needs confirmation, or whether it affects the buffer read by vibeside_telemetry_get. The word 'cached' hints the data is transient, which is the only behavioral signal offered.

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 sentence with the verb front-loaded and zero filler. Every clause enumerates a distinct piece of state being cleared, so 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 parameterless, destructive tool with no annotations and no output schema, the description covers what is cleared but not the consequences: whether cleared records can be recovered, whether the session continues logging afterward, or what the caller observes. Adequate but with a clear gap.

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?

Zero parameters, so there is nothing to document and no risk of under-specification; baseline 4 applies. The schema is trivially complete at 100% coverage.

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?

Specific verb ('Clear') plus the exact resource categories it operates on: cached console logs, runtime errors, and network failure records. This distinguishes it from the sibling clear tools vibeside_clear_dom_telemetry and vibeside_clear_media_telemetry, though it never names them explicitly.

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 statement of when to invoke this versus vibeside_telemetry_get, vibeside_hmr_clear, or the other clear_* siblings. Usage is only implied by the verb. An agent must infer that this wipes the buffer that vibeside_telemetry_get reads.

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