Ensure environment

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

Annotations declare the operation is not read-only but not destructive, and the description adds meaningful context beyond them: the default PyTorch CUDA-12.4 wheels choice, that the build happens automatically with zero manual steps, and that a preview/confirm gate protects the mutation. It omits anything about duration, failure modes, or what the confirm gate returns.

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?

A single front-loaded sentence with zero waste, and the key operational facts (auto-build, default wheels, dry-run/confirm flow) are packed in ahead of any detail an agent needs.

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 mutation tool with no output schema and 9 low-documented parameters, the description covers the overall flow and safety gate but leaves the majority of parameter semantics unaddressed. It is adequate to know what the tool does, but not complete enough to call it well without opening the schema.

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 22% across 9 parameters, so the description must carry the semantic load. It clarifies dryRun, confirm, and the framework default (PyTorch CUDA-12.4), but says nothing about python, account, envName, packages, or profile, leaving most parameters undocumented in both places.

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?

States a specific verb ('ensure exists'), the resource (conda environment for a project), and the auto-build behavior when missing. This clearly distinguishes it from siblings like ris_list_conda_envs, ris_inspect_conda_env, and ris_submit_conda_env_job, which list, inspect, or run in an env rather than create one.

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 describes the two-phase workflow: 'dryRun preview by default; confirm to build,' which tells the agent how to invoke it safely. It does not, however, state when to prefer this over alternatives such as ris_create_project or a conda-env submission job, so it stops short of full when/when-not guidance.

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