clone_container

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

Discloses that the tool returns a UPID or final task status when wait=True, but fails to explain other behavioral traits like whether the source container must be stopped, whether linked clones are supported (despite 'full' parameter), or any side effects. No annotations to compensate.

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 a single sentence, concise but too minimal. It is front-loaded with the core action and return info, but every sentence does not earn its place due to missing critical details.

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?

Given 10 parameters, no schema descriptions, no annotations, and a complex cloning operation, the description is severely incomplete. It omits parameter meanings, behavioral details, and prerequisites, leaving the agent underinformed.

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?

With 0% schema description coverage, the description must explain parameters. It only mentions 'wait' behavior. The required 'extra' parameter is unexplained, and optional parameters like 'full' and 'target' are not described.

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?

Description clearly states 'Clone an LXC container', providing a specific verb and resource. It distinguishes from sibling 'clone_vm' by specifying container type. However, it lacks details on the nature of cloning (full vs linked).

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?

No guidance on when to use this tool versus alternatives like 'create_container' or 'clone_vm'. No prerequisites or context for invocation provided.

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