Validate a full workflow

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

With no annotations, the description takes on the burden of disclosure. It transparently lists the validation categories, which is good, but it does not disclose the output format (e.g., list of errors, boolean, exit code) or any behavior like whether it modifies the workflow. Since there is no output schema, this missing return-value information is a gap.

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 a single, well-structured sentence with a colon introducing the list of validation checks. Every word is informative with no filler, and the most important phrase 'Full validation' is front-loaded.

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?

The listing of checks provides a good overview, but the tool is complex (validates many aspects) and lacks annotations and an output schema. The description does not explain what the result or error report looks like, nor does it explicitly relate to sibling validators. It is sufficient for a basic understanding but incomplete for a fully self-contained tool.

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?

The schema has 0% description coverage, so the description must compensate for the sole 'workflow' parameter. It only calls it an 'n8n-format workflow' and does not explain the expected structure, required fields (nodes and connections), or how to construct it. The schema already provides the type structure, but the description adds minimal value for parameter usage.

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 it performs full validation of an n8n workflow and enumerates the specific checks (unknown node types, required fields, connection structure, cycles, unreached nodes, missing trigger, expression brace balance). This distinguishes it from the more specific sibling validators like validate_node, validate_workflow_connections, and validate_workflow_expressions.

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 comprehensive validation through the word 'Full' and the list of checks, but it does not explicitly state when to use this tool over alternatives like validate_workflow_connections or validate_workflow_expressions. No exclusions or prerequisites are mentioned.

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