update_workflow_json

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether this is destructive (replace_updatable presumably overwrites data), whether changes are reversible via rollback_workflow, what confirm does, or what permission is required. For a mutation tool with a nested 'workflow' object, this is a serious 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 single short sentence with no padding, so it is concise. However, brevity here reflects under-specification rather than efficient communication — the sentence is front-loaded but omits everything an agent needs beyond the bare verb and resource.

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 mutation tool with a nested object parameter, an enum mode, a confirm flag, no annotations, and no output schema, the description is far too thin. It offers a faint hint of the merge/replace duality but omits destructive-behavior disclosure, mode selection guidance, and any parameter meaning.

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% across 4 parameters. The phrase 'full or partial workflow object' loosely gestures at the merge/replace_updatable distinction, but the description never names mode, confirm, or workflow_id and adds no format or constraint detail. It compensates only marginally for the complete absence of schema documentation.

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 names a verb ('Updates') and resource ('workflow'), which is adequate but generic. It does not differentiate this tool from siblings like patch_node_params, duplicate_workflow, or rollback_workflow, all of which also modify workflow state. An agent cannot tell from this sentence why it would use update_workflow_json over those alternatives.

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 about when to use this tool versus patch_node_params, duplicate_workflow, or create_workflow. Critically, the mode parameter offers 'merge' vs 'replace_updatable' semantics, and the description gives no indication of when each applies, despite 'full or partial' hinting at exactly this distinction. No prerequisites or exclusions are stated.

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