Trigger webhook

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

No annotations provided, so description must fully disclose behavioral traits. It mentions triggering a workflow but lacks details on rate limits, authentication requirements, failure behavior, or idempotency. Minimal disclosure beyond the basic operation.

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?

Extremely concise—three short sentences, each adding critical information. No fluff, front-loaded with the core action.

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?

With 5 parameters (one required) and nested objects, the description covers webhookPath and isTest well but does not elaborate on data, headers, or method usage. Schema covers these, so it's nearly complete; minor gap in explaining data/headers structure.

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 100%, so baseline is 3. Description adds value by clarifying the purpose of isTest ('for test webhooks') and webhookPath ('path configured in the Webhook node'), going beyond schema descriptions.

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?

Clearly states the verb 'trigger' and resource 'workflow via its webhook URL'. Differentiates from sibling tools like n8n_execute_workflow and n8n_activate_workflow by specifying the webhook mechanism.

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 clear context on using isTest for test webhooks and mentions webhookPath configuration, but does not specify when to use this tool versus alternatives like n8n_execute_workflow.

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