importVarsCreate multiple environment variables in bulk, skipping keys that are already set.
Bulk-create environment variables, skipping keys already set
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| region | No | ||
| appSlug | Yes | ||
| requestBody | No | The JSON request body. | |
| workspaceSlug | Yes |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-readonly, open-world, and destructive hints. The description adds the specific behavior 'skipping keys already set' which is not covered by annotations, providing useful transparency about idempotency and non-overwrite semantics.
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 concise sentence with no fluff. It immediately conveys the core purpose and a key behavioral nuance, fitting within the ideal length.
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 has nested objects and no output schema, the description provides only minimal context. It lacks details on response format, error handling, partial failure behavior, or parameter relationships, so an agent may need to infer from the schema or sibling tools.
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 only 20% (only requestBody has a generic description). The description does not compensate for the lack of explanations for env, region, appSlug, or the entries array structure, leaving significant ambiguity for an agent.
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 states a specific verb and resource: 'Bulk-create environment variables' clearly distinguishes it from the single-item createVar tool and other variable-related operations. It also notes the 'skipping keys already set' behavior, which is a distinctive feature.
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 when to use it (when needing to create multiple variables at once) and the skip-existing behavior guides selection over createVar. However, it does not explicitly name alternative tools or state when not to use it, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.