vibeside_delete_session_snapshot

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

With no annotations, the description carries the full burden, yet 'safely delete' is never defined and no disclosure is made about whether deletion is reversible, whether the profile must exist, or what permissions are required. It does add that the target is an encrypted file in a vault, which is useful context, but a destructive mutation with zero annotation coverage needs far more.

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 the action and scope front-loaded and no wasted words. It is efficient, though its brevity is partly the reason for the transparency and usage gaps.

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 destructive tool with no annotations, no output schema, and no return-value guidance, the description is too thin. An agent cannot tell from it whether the deletion is recoverable or what happens on failure, which are the key facts for a delete operation.

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 profileName (including its default to the active profile) and snapshotName. The description adds nothing about either parameter, 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 gives a specific verb ('delete') and resource ('session snapshot file') plus the storage location ('vault'), so an agent immediately knows what it does. It does not explicitly name its siblings (restore/list/save session snapshot), leaving differentiation to the shared name prefix, so it falls short of a 5.

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?

There is no statement of when to use this tool versus vibeside_save_session_snapshot, vibeside_restore_session_snapshot, or vibeside_list_session_snapshots. The agent must infer the trigger from the tool name alone, and no prerequisites or exclusions are given.

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