Validate a live workflow by id

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

No annotations are provided, so the description carries the burden. It discloses that the tool fetches and runs 'full local validation', implying a read-only operation without execution. However, it does not describe what happens on invalid/nonexistent ids, whether the operation is non-destructive, or what the return structure is. The phrase 'same checks as validate_workflow' adds context but relies on knowledge of another tool.

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 sentence that is efficient and front-loaded. It communicates the core action, the source, and the validation method without unnecessary words. The parenthetical 'same checks as validate_workflow' is valuable context and earns its place.

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 simple tool with one parameter and no output schema, the description provides a reasonably complete picture: it fetches a workflow by id and validates it locally. It does not mention return values or prerequisites (e.g., connection setup), but these are implicitly covered by the tool name and sibling context. The description is sufficient for an agent to understand the tool's role and basic execution.

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 input schema has a single required string 'id' with no description (schema description coverage 0%). The description says 'by id', which gives minimal semantics—it's a workflow id on the connected instance. However, it does not specify where the id comes from (e.g., n8n_list_workflows) or any format requirements. The description only partially compensates for the lack of schema documentation.

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 uses a specific verb+resource combination: 'Fetch a workflow from your connected n8n instance by id and run full local validation against it.' This clearly distinguishes it from siblings like n8n_get_workflow (fetch only) and validate_workflow (presumably works on provided workflow definitions). The phrase 'same checks as validate_workflow' ties it to an existing sibling but does not explicitly spell out the differentiator beyond the 'by id' fetch.

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 the use case: when you have a workflow id and want to validate the live workflow on the n8n instance. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it (e.g., if you have a workflow definition, use validate_workflow directly). The reference to validate_workflow is helpful but lacks explicit exclusions or alternative guidance.

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