n8n_trigger_webhook

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool makes a real end-to-end invocation and returns the actual response, and it warns about the test-mode vs. active-mode requirement. It could go further in noting potential side effects of executing the workflow, but the essentials of what the tool does are clear.

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 well-crafted sentences: the first states the tool's purpose, and the second provides the crucial conditional guidance for the test parameter. No filler or redundancy, and the most important operational caveat is front-loaded in the second sentence.

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 4 parameters, no output schema, and no annotations, the description does a good job covering purpose, execution mode, and the active requirement. It doesn't explain error cases (e.g., nonexistent path or inactive workflow), but those are secondary to correct invocation. The 'see the real response' phrase adequately covers the return value expectation.

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 baseline is 3. The description adds value beyond the schema by explaining when test=true is appropriate, which is a meaningful behavioral condition. It also reinforces the default method concept, though the schema already documents that.

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 states a specific verb ('Call'), a precise resource ('a Webhook-trigger workflow on the n8n instance'), and a clear goal ('test it end-to-end and see the real response'). It effectively distinguishes this tool from the many workflow-management siblings by focusing on triggering and testing rather than CRUD operations.

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 offers explicit conditional guidance: use test=true only during 'Listen for test event' mode, otherwise the workflow must be active. This tells the agent when a particular parameter setting is appropriate. While it doesn't explicitly name alternatives, no sibling tool provides a direct triggering alternative, so the context suffices.

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