neurover_clone_workflow

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so a baseline of safety context exists. The description adds nothing beyond 'makes a copy' – it does not say what gets copied (graph, nodes, media references, settings), whether the copy lands in the same account, or what identifier comes back. Since the tool is a write that reaches a remote service, this silence is a real gap.

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?

A four-word sentence fragment is technically concise and front-loaded, but the sizing problem here is under-specification rather than verbosity. No structure, no differentiation, no detail an agent could act on beyond the tool name.

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?

For a non-read-only, open-world mutation tool with zero parameter documentation and no output schema, one short sentence is completely inadequate. Nothing tells the agent what a successful clone produces or how to reference it afterwards.

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% for two parameters, so the description carries the full explanatory burden and does not meet it. The word 'копию' faintly implies workflowId identifies the source canvas, but the optional 'account' parameter is entirely unexplained in both schema and description. Only the barest hint of parameter meaning is added.

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 states a specific verb plus object ('Создать копию полотна'), so the agent can tell this duplicates something. However, it calls the resource 'полотно' (canvas) while the tool name says 'workflow', and it never distinguishes the operation from sibling copy-like tools such as neurover_create_workflow or neurover_node_duplicate. The intent is inferable but not sharply scoped.

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 when-to-use guidance at all: nothing says whether this is the right call instead of creating a workflow from scratch or duplicating individual nodes. No preconditions (account selected, workflow existing) are mentioned. The agent must guess from the name alone.

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