Create Bruno Environment

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that the tool writes the whole file, refuses existing names rather than overwriting, reports which existing variables would be deleted, and explains the remedy. This gives the agent a strong sense of the mutation risk and failure modes.

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, focused sentence that front-loads the primary purpose, then packs the critical caveat and resolution options into a well-structured clause. There is no filler or repetition; every phrase 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?

Given the lack of annotations and output schema, the description covers the essential behavioral context: creation, overwrite refusal, error details, and interaction with update_environment. Combined with the rich parameter schemas, the agent has everything needed to invoke the tool safely and choose the right alternative.

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 coverage is 75%, so the schema already explains most parameters in detail, including the two forms of variables and the overwrite flag. The description adds practical meaning by tying overwrite to the retry path after a refusal, and by mentioning 'which ones a replace would delete,' which helps the agent interpret the consequences of setting overwrite.

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 opens with a specific verb and resource: 'Create an environment file for a Bruno collection.' It also distinguishes the tool from sibling update_environment by highlighting that existing names are refused rather than overwritten, clarifying its unique scope.

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?

Explicitly provides guidance for the main conflict scenario: when a name already exists, the agent is directed to choose between merging via update_environment, picking another name, or retrying with overwrite: true. This names a concrete alternative and gives clear when-not-to-use context, going beyond a generic 'use for creation.'

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