Clone Flow

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

With no annotations, the description carries the full burden of disclosure. It only states the basic action without revealing important details such as whether it creates a deep copy, how it handles nodes, side effects on the original, required permissions, or the response format.

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 with no extra words. However, it is too minimal to be fully helpful, which slightly reduces the score from a perfect 5.

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 absence of annotations and output schema, and only 2 parameters, the description should provide more context such as parameter explanations, return value, and behavioral caveats. It falls short of being complete.

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?

The input schema has two parameters ('sourceId' required, 'label' optional) with 0% schema description coverage. The description does not explain either parameter, leaving the agent to infer that 'sourceId' is the flow to clone and 'label' might be the new name. This is insufficient for correct invocation.

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 ('an existing flow tab'). This distinguishes it from sibling tools like 'create', 'update', 'delete', etc., which perform different operations on flow tabs.

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 is provided on when to use this tool versus alternatives such as 'create' for a new flow or 'update' for modifying an existing one. The description lacks prerequisites or context for deciding between clone and other flow-related operations.

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