n8n_execute_workflow

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

Annotations cover key traits (readOnlyHint=false, destructiveHint=false, etc.), but the description adds valuable context beyond annotations: it specifies that the workflow does not need to be active, mentions the return of an execution ID for progress tracking, and clarifies the tool's utility for testing or API-driven scenarios. No contradictions with annotations are present.

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 front-loaded with the core purpose in the first sentence, followed by utility and key behavioral details, all in three concise sentences with no wasted words. Each sentence adds distinct value, making it efficient and well-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 moderate complexity (2 parameters, no output schema, annotations present), the description is largely complete: it covers purpose, usage context, key behavioral traits, and return value. However, it lacks details on error handling or execution limits, which could be useful given the openWorldHint annotation and lack of output 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 100%, so the schema already documents both parameters (id and data). The description adds minimal semantic value by noting that data is 'optional input data passed to workflow start node,' but this largely reiterates the schema. Baseline 3 is appropriate as the schema handles most parameter documentation.

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 trigger workflow execution') and resource ('workflow'), distinguishing it from siblings like n8n_activate_workflow or n8n_get_workflow by emphasizing manual triggering without requiring webhooks or active status. It explicitly mentions optional input data and returns an execution ID, making the purpose highly specific and differentiated.

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?

The description provides clear context on when to use this tool ('Useful for testing or API-driven workflows without webhooks'), but it does not explicitly state when not to use it or name alternatives. For example, it doesn't contrast with n8n_retry_execution or n8n_get_execution, leaving some ambiguity in sibling tool selection.

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