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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description adds real context: atomicity, that invalid graphs are rejected before persistence, and that active-lead safety is still enforced by the backend. It stops short of describing concurrency/rate-limit behavior or undo semantics.

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?

Every sentence carries information — mode semantics, validation behavior, safety guarantee, and post-write optimization — and the core 'atomically patch or replace' statement is front-loaded. Slightly dense, but no filler.

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 complex nested mutation with an output schema present, the description covers the essentials: the two modes, validation-before-persistence, safety enforcement, and post-write optimization. Return values are the output schema's job, so omission there is fine; only cross-sibling positioning is thin.

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 only 33%, so the description must compensate, and it does for the critical parameters: it explains mode semantics and that patch edges 'replace the non-anchor edge set when supplied'. It also notes the optional split-node optimization. It does not add meaning for workflowId or the graph/patch node subfields beyond what the schema shows.

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 (edit/patch/replace) and a precise resource (one workflow graph), and it distinguishes the two modes up front. An agent can tell this apart from the metadata-oriented campaignstack_edit_workflow without opening either schema.

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?

It clearly explains the two operating modes — replace supplies the full graph, patch starts from the current graph and upserts/removes nodes — which tells the agent which mode to choose. It does not, however, state when to prefer this tool over sibling workflow tools like campaignstack_edit_workflow.

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