n8n-mcp

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions 'write_mode' requirement but doesn't disclose whether execution is destructive, reversible, or has rate limits. For a tool that likely performs significant operations, this is inadequate transparency.

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 efficiently structured in two sentences: first stating the core function, then adding a critical requirement. Every word serves a purpose with no redundancy or unnecessary elaboration.

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 tool's complexity (executing workflows with validation), no annotations, and 0% schema coverage, the description is incomplete. While an output schema exists, the description should provide more context about execution behavior, outcomes, and error conditions for adequate understanding.

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 0%, so the description must compensate but adds minimal parameter context. It mentions 'optional test data' but doesn't explain what test data should contain or how workflow_id is obtained. The two parameters remain largely undocumented beyond their names.

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 action ('execute a workflow') and purpose ('for end-to-end validation'), distinguishing it from sibling tools like 'activate_workflow' or 'create_workflow'. However, it doesn't specify what 'execute' entails compared to similar operations like 'retry_execution' or 'stop_execution'.

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 implies usage for validation with test data, but provides no explicit guidance on when to use this tool versus alternatives like 'trigger_webhook_test' or 'retry_execution'. The 'Requires write_mode' note hints at a prerequisite, but doesn't clarify context or exclusions.

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