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

Annotations declare readOnlyHint=false and destructiveHint=false; the description reinforces this by explaining that with workflow_id the original is preserved and a copy suffixed "(updated)" is created — genuinely useful, non-obvious behavior. It also discloses the permission requirement for activate. It does not state what is returned (notably the new workflow's ID), which matters for chaining after a copy is created.

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?

Behavioral core is front-loaded in three short sentences, followed by a compact Args block whose entries add meaning rather than restate the schema titles. No filler sentences.

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?

There is no output schema, and the description never says what a successful call returns — a real gap for a tool that creates a brand-new copy, since the agent needs the new ID to continue. The free-form nested workflow_json structure is also unaddressed, and no sibling for validation (validate_workflow) is suggested before deploying.

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 carry the load, and it documents all three parameters in an Args block — including the non-obvious copy semantics of workflow_id and the permission requirement for activate. The remaining gap is workflow_json, described only as 'the complete workflow JSON' despite being a free-form nested object with additionalProperties, so its expected structure is left unspecified.

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 (deploy/save) and resource (workflow to n8n), then immediately disambiguates two modes: create-new without workflow_id, copy-on-update with workflow_id. It explicitly names the sibling it is not (update_workflow_partial), so an agent can distinguish it from update/deploy siblings without opening any 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?

Gives explicit when-to-use guidance for both branches and names the alternative (update_workflow_partial) with the condition that selects it (in-place edits). It also flags the prerequisite for the activate path (needs delete/activate permission), leaving little to inference.

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