n8n_execute_workflow

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

With no annotations provided, the description carries the full burden. It successfully conveys that the operation returns an execution ID immediately and requires separate polling for results, implying asynchronous behavior. However, it lacks details on error handling, timeouts, or authorization requirements.

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 appropriately brief with two focused sentences. The '[UNIFIED]' prefix appears to be metadata noise, but the core content is front-loaded and every sentence provides value. It efficiently communicates purpose and next steps without redundancy.

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 two-parameter execution tool without output schema, the description adequately covers the high-level operation and return value. However, the complete absence of parameter semantics documentation prevents this from scoring higher, as the agent cannot infer valid inputs for 'site' or 'workflow_id' from either the schema or description.

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?

The input schema has 0% description coverage for both 'site' and 'workflow_id' parameters. The description fails to compensate by explaining what 'site' refers to (e.g., instance URL, project name), what format the workflow_id takes, or providing examples. This is a critical gap for agent usability.

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 specific action ('Manually execute a workflow') and the return value ('return execution ID'). It effectively distinguishes this from siblings like 'n8n_execute_workflow_with_data' by implication (this is the basic execution without data injection) and explicitly references 'get_execution' for status checking.

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?

Provides explicit guidance on the follow-up action ('Use get_execution to check status and results'), which helps the agent understand the async/non-blocking nature of the operation. However, it does not explicitly differentiate when to use this versus 'n8n_execute_workflow_with_data' (which likely accepts input data).

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