workflow.clone

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only says 'Clone workflow' with no details on side effects (e.g., whether the original workflow is modified, whether undo history is affected, or if cloning triggers analysis re-runs). The description is entirely insufficient for the agent to understand behavioral implications.

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?

Although extremely short (two words), this is under-specification, not conciseness. The description fails to deliver any useful information beyond the tool name, making it essentially wasted space.

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 the tool has 3 parameters, no output schema, and zero annotations, a one-phrase description is completely inadequate. The agent cannot determine how to invoke this tool correctly or what the expected outcome is, especially among 70+ sophisticated siblings.

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 0%, meaning the schema provides no documentation for any of the 3 parameters. The description does nothing to compensate: it mentions neither the purpose of session_id, name, nor the register boolean flag. The agent has no clue what semantics these parameters have.

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 is a tautology: 'Clone workflow' restates the tool name without providing any additional detail about what cloning a workflow entails. It does not specify whether cloning creates a new workflow in memory, saves to a file, or duplicates within a project. No distinction from siblings like workflow.list, workflow.describe, or workflow.insert.

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?

There is no guidance on when to use this tool versus alternatives such as workflow.insert or workflow.insert_after. No context is provided about prerequisites (e.g., must have an existing workflow selected or loaded) or when cloning is preferred over other workflow manipulation.

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