n8n_trigger_workflow

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. It indicates a side-effectful action ('kick off' a pipeline) but does not disclose potential consequences, authentication requirements, or response behavior. The schema mentions waitForResponse semantics, but that is schema text, not the description. This lack of transparency for a triggering action is a significant gap.

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 two sentences, front-loaded with the primary action. Every sentence earns its place: the first states the core functionality, the second illustrates applicability. No filler or 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?

The tool is moderately complex with a webhook trigger and optional waitForResponse, but the schema covers parameters well. The description lacks guidance on follow-up actions, such as using n8n_get_execution_status to monitor the triggered workflow, and does not mention error handling or authentication context. It is adequate but leaves gaps that could affect an agent's end-to-end usage.

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 each parameter is already documented in the schema. The description adds a brief example use case (Jira issue key) but does not expand meaningfully on parameter semantics beyond what the schema provides. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 identifies the action ('Trigger a specific n8n workflow by its webhook URL') and the resource (n8n workflow). It also distinguishes from sibling tools by focusing on triggering rather than status retrieval, and provides a concrete use case involving the Salesforce pipeline.

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 implies when to use the tool ('to kick off the full Salesforce automation pipeline') and gives a concrete example (sending a Jira issue key). It does not explicitly state exclusions or alternatives, but the context with n8n_get_execution_status suggests it is the entry point followed by status checks. A clear 'when not to use' is absent, leaving it slightly below explicit guidance.

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