n8n_update_partial_workflow

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

Adds substantial behavioral context beyond annotations: describes best-effort mode for continueOnError, required fieldPath for patchNodeField, and references detailed documentation. Annotations (idempotentHint, readOnlyHint) are consistent and not contradicted.

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 concise but tries to list many operation types inline, making it slightly dense. The first sentence clearly states purpose, but the middle could be streamlined by referencing documentation for full list. Still functional.

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, validation, error handling), the description covers core functionality, key parameter nuances, and behavior for continueOnError. Lacks return value details for normal execution, but overall sufficient.

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%, and description enriches parameters by explaining operations array format, required 'type' field, and specific details for patchNodeField (fieldPath, patches). This adds value beyond the schema's basic descriptions.

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 specific operation types, making the purpose unambiguous and distinguishing it from sibling tools like n8n_update_full_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?

While the description implies partial updates vs. full replacement, it does not explicitly state when to use this tool over alternatives like n8n_update_full_workflow or n8n_create_workflow. No exclusions or context for selection are provided.

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