Clone an agent to disk

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

No annotations, so the description carries the behavioral load. It discloses the auth requirement and a concrete side effect (records .mcs/cs-sync.json for cs_check_drift and cs_push preflight), but omits whether existing local folders are overwritten or what permissions are needed.

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 compact sentences, front-loaded with the core action; the prerequisite and side-effect details each add useful information without padding.

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?

With no annotations and no output schema, the description covers the critical auth prerequisite and sync-stamp side effect, but leaves componentCollections undocumented and does not explain sync-workspace setup or overwrite behavior, making it only minimally complete for a 5-parameter tool.

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 coverage is 60%; the description clarifies outputDir as the parent of the agent-named subfolder but does not explain componentCollections or add much beyond the schema for bot, displayName, and environment.

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 (download/clone) and resource (an existing agent) and the destination (a subfolder named after the agent under outputDir). It clearly differentiates from creation/deletion siblings by being a clone-to-disk operation.

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 prerequisite ('Needs a pac auth profile') and implies the context (a sync-connected workspace), but does not name alternatives like cs_pull or cs_extract_agent_template or state when not to use it.

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