Copy one environment over another

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

With no annotations, the description carries the full burden and does so well: it discloses the destructive nature ('Everything in the target is replaced'), the confirm safety gate, the dry-run default, that it mutates a live environment, and the underlying command/auth mechanism. It stops short of documenting async/background termination or failure behavior.

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 short and front-loads the core action, but it is redundant: 'requires confirm: true' appears twice, and the final sentence 'Mutates a live environment' largely overlaps with 'Everything in the target is replaced.' Two of the three sentences could be merged without losing information.

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?

The safety-critical context is well covered: destructive scope, confirm gating, dry-run behavior, and execution mechanism are all stated. However, with 12 parameters, no output schema, and no description of what the call returns (e.g., status message, jobId, or async behavior), an agent is left guessing about the result contract.

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 100%, so the baseline is 3 and the schema already documents all 12 parameters. The description reinforces the confirm parameter's role ('requires confirm: true') but adds no parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource: 'Copy a source environment onto a target environment,' plus the defining consequence 'Everything in the target is replaced.' This clearly identifies the action and makes it distinguishable from admin siblings like delete, reset, or backup, though it does not explicitly name a sibling or contrast condition.

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 gives operational guidance: to actually mutate you must pass confirm: true, otherwise it is a dry run, and the operation runs via 'pac admin copy' with the active pac auth profile. However, it never states when to choose this tool over alternatives (e.g., cs_admin_reset_environment or cs_admin_restore_environment) or any exclusions.

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