n8n_test_workflow

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which the description does not contradict. The description adds transparency by stating it auto-detects trigger type and supports webhook/form/chat, but it does not detail behavior like waiting for response or error handling. Overall, it provides useful context beyond annotations.

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 extremely concise: two sentences plus a note. It front-loads the purpose and immediately provides actionable details. Every sentence is essential, with no fluff or repetition.

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 complexity of 10 parameters with conditional behavior across trigger types, the description covers the core functionality well. However, it does not explain the output or return value (no output schema), and it could better detail parameter usage per trigger type. Still, the schema descriptions compensate, making it reasonably complete.

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?

With 100% schema description coverage, the input schema already documents each parameter thoroughly. The description adds value by summarizing supported trigger types and auto-detection, but it does not explain parameter relationships or conditional usage (e.g., which parameters apply to which trigger type). It meets the baseline for high coverage.

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 tool's purpose: 'Test/trigger workflow execution.' It specifies auto-detection of trigger type and lists supported types (webhook, form, chat), which distinctively sets it apart from sibling tools that edit, validate, or retrieve workflows.

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 a clear context for when to use the tool (testing/triggering workflows) and includes a constraint note about external execution only for specific trigger types. However, it does not explicitly address when not to use the tool or mention alternatives among sibling tools, leaving some ambiguity.

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