n8n_test_workflow

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description correctly implies execution is non-read-only but not destructive. It adds context about trigger type auto-detection and external execution limitations, going beyond annotations. No contradiction with 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 three sentences, each serving a distinct purpose: purpose statement, auto-detection and support, and a critical usage note. It is front-loaded with the verb and resource. No extraneous information.

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 10 parameters, many conditional, and no output schema, the description is too brief. It fails to explain what the tool returns (e.g., execution ID, status) or the behavior differences between trigger types. While the schema is detailed, the description does not sufficiently tie parameters to outcomes, leaving gaps for an agent.

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 baseline is 3. The description adds value by grouping parameters by trigger type (webhook, form, chat) and explaining auto-detection of triggerType, which helps the agent understand conditional requirements beyond the schema's individual 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?

The description clearly states the tool's purpose: 'Test/trigger workflow execution.' It specifies supported trigger types (webhook, form, chat) and distinguishes itself from sibling tools like n8n_executions (which list executions) and n8n_create_workflow (which creates workflows). The verb 'test' aligns with the tool's role in the toolset.

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 contextual guidance: 'Only workflows with these trigger types can be executed externally,' indicating when not to use the tool. It also mentions auto-detection of trigger type. However, it does not explicitly name alternative tools for non-triggerable workflows, missing an opportunity for clearer differentiation.

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