vibekit_set_env

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

With no annotations, the description carries the full burden. It discloses one behavioral trait (changes take effect on next restart), but does not explain whether existing variables are overwritten, whether the operation is additive, or any permission requirements. This leaves significant ambiguity for a mutation tool.

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?

Two concise sentences with no filler. The purpose is front-loaded and the restart note is valuable information that 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?

The tool is simple with two well-described parameters, but the absence of annotations and minimal behavioral disclosure (no mention of merge vs replace) makes it less complete than ideal. The restart note helps, but an agent may still be uncertain about side effects.

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% and both parameters have clear descriptions (appId 'App ID or subdomain slug', vars 'Key-value pairs to set...' with example). The description text adds no additional parameter meaning, so 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 clearly states 'Set one or more environment variables for a hosted app', which specifies a specific verb, resource, and scope. It naturally distinguishes from sibling tools like vibekit_app_env (view) and vibekit_delete_env (delete).

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 use case (setting env vars) but does not explicitly state when to use vs alternatives. The note about changes taking effect on next restart provides a timing consideration, but there is no mention of when not to use or reference to sibling tools.

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