n8n_validate_workflow

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

The annotations already declare readOnlyHint=true, and the description is consistent with that by describing a non-mutating validation operation. The description adds useful behavioral detail by enumerating what is checked (node names, types, required parameters, connections), which goes beyond the read-only annotation. It stops short of describing how errors or validation results are returned, but the safety profile is already covered by 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 tight, front-loaded sentences. The first establishes the purpose and scope, and the second gives a direct invocation rule. Every sentence earns its place with no filler.

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?

For a read-only validation tool, the description explains what it validates and when to call it. The main gap is that there is no output schema and the description does not state what the tool returns on success or failure, which an agent might need to interpret the validation result. Still, the invocation context is clear and complete enough for most use.

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?

Only one parameter (workflowId) has a schema description, giving roughly 25% schema_description_coverage. The description does not compensate by explaining the role of name, nodes, or connections, nor the relationship between passing a workflow JSON and using workflowId to validate an existing stored workflow. The parameter names are somewhat self-explanatory, but the description leaves the semantic burden mostly on the schema.

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 states a specific verb ('Validate'), the resource ('workflow JSON'), and the exact validation scope: node names, types, required parameters, and connections. It also positions the tool relative to mutation workflows, so an agent can distinguish it from n8n_create_workflow, n8n_activate_workflow, and n8n_autofix_workflow.

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 explicitly directs the agent to call this tool before n8n_create_workflow or n8n_activate_workflow, and says it should be used before creating or updating. This gives clear, actionable guidance on when the tool is appropriate and which sibling operations depend on it.

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