Delete Var

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

The description aligns with the destructiveHint annotation and makes the delete operation explicit. It does not detail irreversibility or side effects beyond the annotation, but the annotation already covers destructive behavior, so the description adds sufficient clarity.

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 clear sentence with no unnecessary words. It is direct and easy to parse, making the tool's purpose immediately understandable.

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?

Given the tool's low complexity and the presence of sibling tools, the one-sentence description is reasonably complete. It identifies the resource type and action, though it does not mention return behavior or error cases, which are not critical for this simple 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?

The schema lists parameters like workspaceSlug, appSlug, varId, env, and region, but the description provides no explanation of these fields or how they should be used. The names are partially self-explanatory, but the description does not compensate for the lack of parameter-level documentation.

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') and the target resource ('an environment variable or credential'). This distinguishes it from sibling tools like listVars, createVar, updateVar, and revealVar by the verb and intent.

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 tool is used when an environment variable or credential should be removed, but it does not explicitly state when to prefer this over other var-related tools or mention any preconditions. The sibling list provides context, but the description itself offers no direct usage guidance.

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