neurover_create_workflow

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with them by implying a creation operation. Beyond that it adds only that the new canvas is empty; it says nothing about persistence, whether the new workflow becomes active, or what is returned.

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 single short sentence with no filler and the action front-loaded. It is efficient, though the brevity here reads as under-specification rather than disciplined concision.

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 mutating creation tool with a required parameter, no output schema, and zero schema documentation, the description is too thin. An agent cannot tell what it must supply or what a successful call produces, and must rely on the schema alone.

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% and the description mentions no parameters whatsoever — critically, it never reveals that a `name` string (1-120 chars) is required, nor what `account` selects. With two fully undocumented parameters, the description fails to compensate for the schema gap.

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 single sentence gives a verb and an object (create a new empty canvas), so the action is recognizable. However, it uses "canvas" (полотно) while the tool name and siblings speak of "workflow", and it does not distinguish this from siblings such as neurover_clone_workflow or neurover_workflows, which occupy adjacent territory.

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 to prefer this over neurover_clone_workflow when duplicating an existing graph, nor what preconditions (e.g. an authenticated account) are needed. It is not misleading, but the agent must infer usage entirely.

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