n8n_execute_workflow_with_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to explain execution semantics (sync vs async), return values, error conditions, or side effects like creating execution records.

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 brief at two sentences, but the '[UNIFIED]' prefix wastes space without aiding comprehension. The core content is efficiently structured.

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 (workflow execution with nested data objects), lack of output schema, and zero parameter documentation, the description is insufficient. It omits critical context like return format, authentication requirements, and the nature of the data parameter's schema.

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 0%, requiring the description to compensate. While it mentions 'custom input data' (mapping to the data parameter), it completely omits semantics for 'site' (instance identifier?) and 'workflow_id', and doesn't explain that 'data' accepts freeform JSON (additionalProperties: true).

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 the tool executes workflows with 'custom input data' and specifies it's for 'webhook or manual triggers', which distinguishes it from the sibling n8n_execute_workflow. However, the '[UNIFIED]' prefix is metadata noise that doesn't add value.

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 implies usage context by mentioning webhook and manual trigger workflows, but lacks explicit guidance on when to use this versus n8n_execute_workflow or prerequisites like workflow activation status.

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