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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral value: it is deterministic, makes no AI call, and returns the checked-and-repaired workflow ready to paste. The only mild gap is that it doesn't explicitly say whether repairs are persisted or only applied to the returned copy.

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 front-loaded sentences state what is checked before the return behavior, followed by a short Args note. Every sentence carries information; only the Args block is slightly redundant with the parameter name.

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 one-parameter tool with no output schema and full annotation coverage, the description covers what it validates, that it is deterministic, and what it returns. Minor missing detail on the shape of the input object and whether fixes are persisted keeps it below 5.

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?

With a single nested object parameter at 0% schema coverage, the description only says 'The complete n8n workflow JSON.' That conveys the key constraint (must be complete, not partial) but gives no detail on expected structure such as nodes/connections keys, which matters for a free-form nested object.

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?

States a specific verb (validate/check) and resource (n8n workflow JSON) and immediately enumerates the checks performed: connections/orphaned nodes, credential structure, node-type casing, AI-node requirements. That level of specificity separates it from generic siblings like autofix_workflow or self_heal_workflow, even without naming them.

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 line 'Applies safe deterministic fixes without any AI call' implies this is the non-AI alternative to the repair-oriented siblings, but no sibling is named and there is no explicit when-to-use/when-not guidance. The agent must infer the routing from the phrase alone.

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