Pause or resume VibeWise learning mode at the user's request, disabling or re-enabling the design-checkpoint gate.
VibeWise: pause learning mode (gate off) at the user's request, or resume it.
| Name | Required | Description | Default |
|---|---|---|---|
| resume | No | true to resume instead of pausing. | |
| projectPath | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It states the mode is (gate off) but doesn't explain what pausing actually affects, whether it is reversible, or what side effects occur. For a state-changing toggle with zero annotation coverage, this is a notable gap.
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 tight sentence with no waste. Front-loads the tool name and the core action. Could be slightly more informative but is appropriately sized for a simple toggle.
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 state-changing tool with no annotations, no output schema, and one undocumented parameter out of two, the description is too thin. It doesn't say what pausing disables, whether it's scoped per project, or what the response looks like.
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 coverage is 50%: the 'resume' boolean is documented in the schema, but 'projectPath' has no description in either schema or tool description. The description adds the pause-vs-resume semantics but does not compensate for the undocumented projectPath parameter.
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+resource: pausing/resuming learning mode. The 'at the user's request' framing clarifies it is a gating toggle. It is clear enough but does not explicitly differentiate from siblings like vibe_start or vibe_status, though 'pause' vs those names is reasonably distinguishable.
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?
Implies usage as a toggle to pause or resume, but provides no explicit when-to-use guidance relative to vibe_start, vibe_reset, or other siblings. An agent has to infer that this is the appropriate tool when it wants to disable learning mode.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.