n8n_update_partial_workflow

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

Annotations provide readOnlyHint (false), destructiveHint (false), and idempotentHint (true). The description lists operation types, revealing mutation and potential non-idempotency (e.g., addNode), which slightly contradicts the idempotentHint. However, the description does not explicitly address behavioral traits beyond what annotations offer.

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?

Description is concise, front-loaded with the main purpose, lists operation types efficiently, and references tools_documentation for deeper detail. No redundant information.

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 (many operation types) and absence of an output schema, the description covers the core behavior. However, it lacks details on error handling, return format, and clarification of idempotency. The reference to tools_documentation partially compensates.

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 100%, so the schema already documents parameters. The description adds value by detailing the patchNodeField operation with fieldPath and patches (find/replace), which goes beyond schema definitions.

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 'Update workflow incrementally with diff operations' and lists operation types. It distinguishes itself from the full update sibling (n8n_update_full_workflow) by implying partial updates, but does not explicitly contrast them.

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 on when to use this tool versus alternatives like n8n_update_full_workflow or other sibling tools. The description references tools_documentation for details but does not provide usage context or exclusion conditions.

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