vibeside_mutate_storage

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

No annotations are provided, so the description carries the full behavioral burden. It signals mutation via 'Set, delete, or clear' but never states that 'clear' wipes an entire storage domain (highly destructive), whether changes persist across reloads/sessions, or what permissions/context are required.

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 list front-loaded and zero filler. It is appropriately sized, though it could have used one more clause to carry the missing behavioral warning.

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 6-parameter mutation tool with nested cookieOptions/indexedDbOptions, no annotations, and no output schema, the description omits the destructive semantics of 'clear', persistence behavior, and any return/error information. The rich schema covers parameters, but the behavioral gap is unaddressed.

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 key, type, value, action, cookieOptions, and indexedDbOptions. The description only echoes the type and action enumerations and adds no extra syntax or constraint detail, so the baseline of 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?

States specific verbs (set, delete, clear) plus the resource (storage items) and enumerates the four storage domains, which matches the `type` enum. It implicitly contrasts with the sibling vibeside_inspect_storage by naming only mutation actions, but it never names that sibling explicitly.

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?

No when-to-use or when-not-to-use guidance. It does not say to prefer vibeside_inspect_storage for reads, nor that a browser connection/session must already exist before mutating storage. Usage is only inferable from the verb list.

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