clone_instance

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

No annotations are provided, so the description must cover behavioral aspects. It only mentions parameters but does not explain what cloning entails (e.g., whether the cloned instance starts automatically, if it shares storage, or any limitations). This is minimal for a complex operation.

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 includes an 'Args' section that lists parameters efficiently. It could be slightly more concise by integrating the parameter descriptions into prose, but overall it is well-structured with no wasted words.

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?

Despite having an output schema, the description lacks context about the cloning process, return values, error conditions, or side effects. For a tool that duplicates an instance, more information is needed for correct invocation, such as whether snapshots are included or if the instance must be stopped.

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 adds basic meaning for both parameters: 'source' is the name of the instance to clone, and 'name' is optional. However, it does not specify constraints (e.g., source must exist, name uniqueness) or provide examples.

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 clearly states the action ('Clone') and the resource ('existing Multipass instance'). It is specific and distinguishable from sibling tools like 'launch_instance' (create new from image) or 'restore_instance' (from snapshot).

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 implies usage (clone an instance) but does not explicitly state when to use it versus alternatives like 'snapshot_instance' or 'restore_instance'. No prerequisites or conditions are mentioned.

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