vibeside_reset_emulation

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

No annotations are provided, so the description carries the burden. It does disclose the mutation's effect and end-state clearly, and the schema flags network/CPU resets as optional via defaults. However it says nothing about side effects on other session state, permissions, or whether resetting is scoped per-tab/per-session.

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. Every clause (viewport, device emulation, optional throttling, default desktop state) adds distinct, useful information.

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 two-parameter reset tool with no output schema and no annotations, the description adequately conveys scope and the resulting state. It could be more complete by noting the tab/session scope of the reset, but nothing essential to correct invocation is missing.

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 both parameters (resetCpu, resetNetwork) are already fully documented, including defaults and target values. The description's phrase "optional network/CPU throttling" mirrors but does not extend that schema information, so the 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?

The description uses a specific verb ("Reset") plus a clear set of resources (viewport, device emulation, network/CPU throttling) and the target end-state ("default desktop state"). An agent can tell it apart from sibling setters like vibeside_emulate_device and vibeside_throttle_cpu, 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 explicit when-to-use, when-not-to-use, or alternative guidance is given. That this undoes prior emulation/throttling from siblings like vibeside_emulate_device is only inferable from the name and the word "Reset"; nothing routes the agent to it directly.

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