vibekit_rollback

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, such as whether the rollback causes downtime, whether the current deployment is preserved, or whether any data or configuration is affected. For a rollback operation, more transparency is 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?

The description is a single concise sentence that immediately communicates the tool's purpose. It is front-loaded and contains no filler or redundant 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?

The tool is a mutation-like operation with no annotations and no output schema. The description adequately covers what the tool does and how to find the deployId, but it lacks important contextual details about rollback behavior (e.g., reversibility, app state, whether it forces a restart). Given the moderate complexity, the description is minimally viable but has notable gaps.

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 input schema already provides descriptions for both parameters, and the deployId parameter description includes a helpful cross-reference to vibekit_deploy_history. This adds value beyond the raw schema fields by explaining how to obtain a valid deployment ID, so the semantic guidance is strong.

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 ('roll back') and resource ('app') and clearly distinguishes the tool from siblings like deploy, redeploy, and deploy_history. It clearly communicates reverting to a previous deployment snapshot, which is distinct from other operations.

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 appropriate context: when you want to revert an app to a previous deployment. It also gives explicit guidance to use vibekit_deploy_history to list available deployments, which helps the agent gather the required deployId. No explicit exclusions or alternative tool comparisons are provided, but the core usage is clear.

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