vibekit_delete_env

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

No annotations are provided, so the description carries the full burden. It only states the deletion action without disclosing whether the operation is irreversible, whether it impacts the running app, or if special permissions are required. The destructive nature is implied by the verb 'delete' but no additional context is given.

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 a single, efficient sentence that front-loads the verb 'Delete' and includes all essential information without any waste. Every word 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?

For a simple two-parameter delete tool with full schema coverage, the description is minimally adequate. However, it lacks any context about post-deletion effects (e.g., triggering a redeploy, irreversibility) or error conditions, which would be helpful given there is no output schema and no annotations.

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%: both 'key' and 'appId' have clear descriptions in the schema. The tool description adds no extra parameter information, but the schema already sufficiently documents the required inputs, 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?

The description clearly states the action (delete), the resource (environment variable), and the scope (from a hosted app). It distinguishes this tool from siblings like vibekit_set_env (which sets) and vibekit_app_env (which likely lists env vars), making the purpose unambiguous.

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 remove an environment variable, but it gives no explicit guidance on when to use this tool over alternatives like vibekit_set_env or vibekit_app_env. No 'when not to use' or alternative tool references are provided.

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