apply_canvas_patch

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses that changes are atomic (all-or-nothing), undoable, and applied to a live canvas. This adds meaningful behavioral context about failure semantics and reversibility, though it doesn't address concurrency conflicts or the role of base_revision.

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, front-loaded sentence with no filler. Every word ('atomic', 'undoable', 'live', 'batch') earns its place by conveying behavioral and semantic constraints.

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 destructive, non-idempotent nature and a complex operations schema with no output schema, an agent needs more context about conflict behavior, base_revision semantics, and typical use cases. The compact description covers a few key properties but leaves major gaps for correct invocation.

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%, and the description does not compensate by explaining canvas_id, base_revision, or the operations array. It only says 'batch of changes,' which maps vaguely to operations but adds no meaning to any specific parameter.

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 specific action ('apply'), a precise resource ('changes to a live ComfyUI canvas'), and adds defining qualifiers ('atomic, undoable batch') that set it apart from the sibling read/search tools. It tells an agent immediately that this is the mutating patch tool for canvas edits.

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 alternatives such as inspect_canvas, present_canvas, search_nodes, or inspect_node_type. The phrase 'apply ... batch of changes' implies mutating use, but it does not state prerequisites, when not to use it, or which sibling might be preferred.

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