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 well: it discloses that the target is fully replaced (destructive), that confirm:true gates the live mutation, and that omitting it yields a dry run. It also names the underlying command and auth profile, though it omits permission requirements and reversibility.

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 destructive warning is front-loaded, which is good, but 'requires confirm: true' is stated twice in near-identical clauses, which is redundant. The 'active pac auth profile' phrasing also oversimplifies the schema's profile default logic (CPS_ADMIN_PROFILE vs CPS_PAC_PROFILE).

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 12-param destructive tool with no annotations or output schema, the description covers the critical behavior (overwrite, confirm gating, dry run). It could note that source/target environments are effectively required even though the schema lists zero required params, but otherwise the agent has enough to act safely.

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 schema already documents all 12 parameters, including sourceEnvironment/targetEnvironment and confirm. The description restates confirm's semantics but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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+resource ('Copy a source environment onto a target environment') and clarifies the overwrite semantics ('Everything in the target is replaced'). This distinguishes it well from create/backup siblings, though it never names a specific alternative like cs_admin_restore_environment or cs_clone_solution to route the agent.

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?

It states the confirm prerequisite and dry-run fallback, but gives no when-to-use vs alternatives guidance despite many adjacent admin tools (cs_admin_restore_environment, cs_admin_create_environment, cs_compare_environments). No exclusions or routing context is provided.

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