Remove forced CSS pseudo-classes from a specific element selector or the entire document to reset UI states for accurate testing.
Clear forced CSS pseudo-classes from a specific element selector or across the entire document.
| Name | Required | Description | Default |
|---|---|---|---|
| selector | No | Specific CSS selector to clear forced pseudo-states from (if omitted, clears all tracked elements) |
Changes observed during successful MCP inspections.
v0.17.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not say whether this mutates the live page, requires an active browser connection, what happens when no pseudo-states are forced, or whether the effect is scoped to the session – all material for a state-mutating 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 well-formed sentence with the subject and both operating modes front-loaded, and no filler. It is terse to the point of omitting useful context, but nothing in it 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?
With no annotations, no output schema, and a state-resetting behavior, the definition leaves key questions unanswered: prerequisite connection, error behavior, and the relationship to vibeside_emulate_pseudo_state. It describes the action but not enough to invoke it confidently.
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 single parameter has 100% schema description coverage, which already explains the omittable selector and the clears-all fallback, so the baseline is 3. The description's 'specific element selector or across the entire document' restates the schema's semantics without adding format or matching details.
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 (forced CSS pseudo-classes) plus its two scopes: a named selector or the entire document. It does not reference its obvious sibling vibeside_emulate_pseudo_state, so an agent gets the purpose but no explicit differentiation.
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?
The description implies the use case (undoing forced pseudo-states) and the two scoping modes, but never says when to reach for this versus vibeside_emulate_pseudo_state, nor whether a prior forced state must exist. Usage is inferable but unstated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.