edb_set_environment_variable

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

Annotations include destructiveHint=true and idempotentHint=true, but the description does not elaborate on potential destructive behavior (e.g., overwriting existing variables). It does clarify that variables are passed to the program, which adds some behavioral context beyond the annotations.

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 relatively concise but includes an Args section that largely duplicates schema information. It is well-structured with clear sections, though it could be slightly more streamlined by removing the formal Args/Returns headers.

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 presence of an output schema (confirmation string) and sibling tools for get/unset, the description is fairly complete. It explains the tool's purpose and effect, though it does not mention whether setting an existing variable overwrites it or if the variable scoping is per-session.

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 input schema already describes the name and value fields, but the description adds concrete examples ('LD_PRELOAD', 'PATH') and explicitly states that these are variable name and value, adding clarity beyond the schema's generic descriptions.

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 ('Set an environment variable'), specifies the target ('debugged process'), and explains the effect ('passed to the program when it runs'). It distinguishes itself from siblings like 'edb_get_environment' and 'edb_unset_environment_variable' through its imperative verb and explicit resource.

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 mentions equivalence to EDB's process environment configuration but does not explicitly state when to use this tool versus alternatives (e.g., when to set vs get vs unset). The guidance is implied by the tool name and function, but no direct comparisons or exclusions are provided.

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