n8n: Execute workflow

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the safety profile is covered structurally. The description adds real value by implying dispatch-then-poll behavior via the execution ID and the get_execution follow-up, but it never mentions side effects, non-idempotency, or permission requirements, so it adds only partial context beyond the annotations.

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?

Two short sentences, front-loaded with the action and then the follow-up step. The '[UNIFIED]' tag and 'Manually' wording are minor waste but nothing obscures the core instruction.

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 destructive, non-idempotent action with two fully undocumented required parameters and no output schema, the definition covers the return value (execution ID) and the polling path but leaves parameter meaning and side-effect risk unaddressed. It is minimally viable but not sufficient to call safely without inspecting the 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 description coverage is 0%, so both required parameters (site and workflow_id) are undocumented everywhere. The description mentions 'a workflow' but gives no format, identifier source, or meaning for site versus workflow_id, so it fails to compensate for the coverage gap.

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 and resource: manually execute a workflow and return an execution ID. It is clear what the tool does, but it never distinguishes itself from the close sibling n8n_execute_workflow_with_data, and the '[UNIFIED]' prefix adds noise rather than meaning.

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 useful next-step guidance (call get_execution to check status and results), which implies execution is asynchronous, but gives no guidance on when to choose this tool over n8n_execute_workflow_with_data or what preconditions must hold before executing.

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