vibe_resume

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

With no annotations, the description carries the full behavioral burden, but it only explains the session-selection logic. It does not describe what continuing a session actually does, whether it executes tools or mutates files, how approval/trust settings affect behavior, or what the agent should expect from the many execution-related parameters.

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 two sentences, front-loaded with the core action and followed by the session-selection rule. There is no unnecessary wording or repetition.

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 16-parameter tool with no annotations and no output schema, the description covers the essential resume-versus-continue routing. However, it leaves out behavioral context around execution, approvals, worktrees, and side effects, so it is minimally adequate rather than complete.

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 the schema already documents all 16 parameters. The description mainly restates session_id and continue behavior already present in the schema and adds no additional meaning for parameters such as agent, trust, worktree, max_price, or auto_approve.

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 states a specific verb and resource: 'Continue a previous Vibe session.' It is clear enough to distinguish resuming from starting a new run, but it does not explicitly name or contrast with the sibling tools vibe_run or vibe_manage.

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?

It gives clear usage guidance for the key choice: provide session_id to resume a specific session, or use continue:true (the default without session_id) to continue the last session for the directory. It does not state when not to use this tool or explicitly route to sibling alternatives.

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