Roblox Clone Instance

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

No annotations are present, so the description carries full burden. It only states the basic action (clone and place under parent) without disclosing side effects, error conditions, copy behavior (e.g., children, properties), or performance implications. This is minimal behavioral information.

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 concise sentence that front-loads the core purpose. However, it lacks additional helpful context that could fit without bloat, resulting in slight under-specification.

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 no annotations, no output schema, and the complexity of cloning Roblox instances (which may involve copying children, properties, etc.), the description is incomplete. It does not address common scenarios like handling invalid paths, naming collisions, or runtime behavior.

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?

All 4 parameters are described in the input schema (100% coverage), so baseline is 3. The tool description adds no extra meaning beyond what the schema already provides (e.g., 'sourcePath' is clearly the source to clone).

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 verb 'clone' and the resource 'instance', and specifies the placement under a target parent. This distinguishes it from sibling tools like roblox_create_instance (create) or roblox_reparent_instance (move).

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 provides no guidance on when to use this tool versus alternatives such as roblox_create_instance or roblox_reparent_instance. No exclusions or context are given, leaving the agent to infer usage without direction.

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