Build conda env

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

With annotations already declaring readOnlyHint=false, destructiveHint=false and openWorldHint=true, the description adds useful detail about resource locality (CPU only, never /home, never a GPU). However, it omits the critical two-step safety flow (dryRun defaults true, confirm must be set) that governs whether a job is actually submitted.

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 no wasted words; the scope and key constraint appear immediately. It is arguably terse for a 12-parameter submission tool, but nothing in the sentence is filler.

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 12 parameters, 33% schema coverage and no output schema, the description is under-powered: it never explains the dryRun/confirm submission gate, the required inputs, or how packages/envFile interact. An agent could call this incorrectly despite the clear opening sentence.

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 33% across 12 parameters, so the description must compensate — and it does not. It says nothing about packages, envFile, python version, walltime, or the required project/envName, leaving most parameters to a sparse schema.

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 names a specific verb (build/update), resource (conda environment), target location (project's envs/) and execution mode (CPU job, no GPU/home). It clearly separates this from read-only siblings like ris_inspect_conda_env, though it never names the closest alternative ris_ensure_env.

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?

There is no guidance on when to use this over ris_ensure_env, ris_submit_python_job, or ris_submit_r_job, and no mention of prerequisites or exclusions. The only constraint given is environmental (CPU/no GPU/no /home), which is context rather than routing guidance.

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