n8n_test_workflow

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

Annotations indicate mutation (readOnlyHint=false) and non-destructiveness (destructiveHint=false). Description adds behavioral context: auto-detection, supported trigger types, and the limitation that only certain workflows can be executed externally. This goes 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?

Two sentences and a note efficiently convey the tool's purpose and key constraint. No redundant information; 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?

Description mentions the crucial constraint on trigger types, which is very helpful. However, it lacks information about return values, error conditions, or detailed behavior for each trigger type. Given the complexity (10 parameters, nested objects), a bit more completeness would be beneficial.

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 briefly summarizes supported inputs (webhook, form, chat) but does not add significant meaning beyond the schema itself. No explanation of parameter dependencies or complex interactions.

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?

Description clearly states the action (test/trigger) and resource (workflow execution). It specifies supported trigger types and distinguishes from sibling tools like n8n_executions or n8n_get_workflow by focusing on execution triggering.

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?

Description includes auto-detection of trigger type and explicitly limits external execution to workflows with specific triggers. While it doesn't compare directly with siblings, it provides enough context for when to use this tool.

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