patch_node_params

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

No annotations are provided, so the description carries the full burden. It does not explain that this is a mutation, whether changes are reversible, what permissions are required, or what the confirm parameter does. For a mutation tool with zero annotation coverage, this is a significant 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 efficient sentence with no wasted words. However, its brevity contributes to the lack of detail elsewhere, though conciseness itself is good.

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 5-parameter mutation tool with nested objects, no annotations, and no output schema, the description is too thin. It does not cover parameter behavior (merge, confirm) or any return or error information.

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%, so the description must compensate. It mentions 'parameters' and 'named workflow node', which hint at the params and node_name parameters, but the merge and confirm parameters are completely unexplained. With five parameters and no schema descriptions, the description is inadequate.

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?

States a specific verb (patches) and resource (parameters on a named workflow node), which is clear and distinguishable from sibling tools like update_workflow_json or set_workflow_active. It does not explicitly differentiate from those siblings, but the scope to node-level parameters is reasonably specific.

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 update_workflow_json. No mention of prerequisites such as the workflow being inactive, or conditions under which patching node params is appropriate.

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