vibekit_agent_reset

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

With no annotations, the description carries full behavioral burden. It discloses the effects of each action (e.g., 'wipe conversation history', 'wipe memory files'), which is good. However, it does not mention irreversibility, potential downtime, or whether cleaning disk affects other apps. It could better warn about destructive consequences.

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 with no fluff. It front-loads the core purpose ('Reset an app's agent') and then efficiently enumerates the actions. Every phrase earns its place.

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?

Despite no output schema, the description provides enough context for selecting an action and understanding its effect. It does not specify return values or confirm what happens after the action, but given the tool's simple two-parameter interface, the description is largely 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?

The input schema already describes both parameters at 100% coverage, but the description adds semantic meaning to the action enum values, explaining that 'clear-sessions' wipes conversation history, 'restart-agent' restarts the gateway process, etc. This goes beyond the schema's bare enum labels.

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 the specific verb 'Reset' with resource 'app's agent', and enumerates four distinct actions with their effects. This clearly differentiates it from sibling tools like vibekit_restart_app (which restarts the app, not the agent) and vibekit_agent_compact (which compacts memory rather than resetting).

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 usage when you need to clear agent session history, memory files, restart the gateway process, or free disk space. It does not explicitly state when to avoid using this tool or mention alternatives, but the action list provides clear context for when each sub-action is appropriate.

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