n8n_update_partial_workflow

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

Annotations indicate non-readonly, non-destructive, idempotent, and open-world. The description adds behavioral details like the required format for patchNodeField (fieldPath and patches array) and references tools_documentation for full details. It does not contradict annotations.

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 paragraph but is front-loaded with the main purpose and lists operation types concisely. It avoids unnecessary words, though could be better structured (e.g., bullet points) for readability.

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's complexity (multiple operation types, parameters for validation and error handling), the description provides a good overview. It references tools_documentation for exhaustive details, which is appropriate. No output schema exists, but the description covers input sufficiently.

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 coverage is 100% with parameter descriptions. The description adds value by explaining the structure of operations array (list of types) and specific requirements for patchNodeField (dot path, patches). This goes beyond the schema's generic description.

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 tool's purpose: 'Update workflow incrementally with diff operations' and lists specific operation types like addNode, removeNode, etc. This distinguishes it from sibling tools like n8n_update_full_workflow which replaces the entire workflow.

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?

The description mentions the tool is for incremental updates and lists operations, but does not explicitly state when to use it versus alternatives (e.g., n8n_update_full_workflow) or provide exclusions. The guidance is implied but not direct.

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