compute.apply_environment

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

Annotations only declare readOnlyHint=false; the description adds real behavioral context beyond that: confirm must be true, writes are restricted to prefixes RCF owns (managed_roots or managed=true), blocker-bearing plans are rejected, and every write is audited. It stops short of describing failure/partial-apply behavior or whether the call blocks until completion.

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?

Three tight sentences, front-loaded with the action and its variants, followed by the confirm gate and the safety constraints. No filler and nothing redundant with the schema.

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 mutating apply tool with no output schema and zero parameter documentation, the description covers the safety envelope well but leaves gaps: what is returned on success, whether the operation is synchronous, and what the caller should do after a blocker refusal. Adequate but not complete.

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 0%, so the schema gives no meaning for any of the three parameters. The description clarifies the one non-obvious semantic — confirm must be true despite the schema defaulting it to false — but says nothing about env_id or node_id semantics or how they pair with the plan.

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 and resource: execute a 'reviewed environment plan', narrowed to conda create/install or venv+pip. 'Reviewed' implicitly points at compute_plan_environment as the prerequisite, so the agent can separate planning from applying, though no sibling is named outright.

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?

Gives a hard precondition ('Requires confirm=true') and a refusal condition ('refuses plans with blockers'), which tells the agent when the call will fail rather than succeed. It does not explicitly say 'run compute_plan_environment first' or describe what to do when blockers are reported, so guidance is strong but not fully closed-loop.

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