n8n_test_workflow

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

Description adds behavioral context beyond annotations (auto-detection of trigger type, supported types). Aligns with readOnlyHint=false and destructiveHint=false. No contradictions.

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?

Three sentences with no wasted words: purpose, supported types, and a crucial limitation. Front-loaded with the verb 'Test/trigger'.

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?

Covers key aspects: purpose, trigger type support, and constraint. Missing details on return value or auth, but output schema is absent and annotations don't require elaboration.

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?

Despite 100% schema coverage, the description groups parameters by trigger type (e.g., message/sessionId for chat, httpMethod/webhookPath for webhook), aiding parameter selection beyond isolated 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 tool tests/triggers workflow execution and auto-detects trigger types (webhook, form, chat). Distinguishes from siblings like n8n_executions by focusing on execution triggering rather than listing.

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 by listing supported trigger types and noting that only workflows with these triggers can be executed externally. Lacks explicit alternatives, but the constraint implicitly guides usage.

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