n8n-diagnose

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions checking container status, analyzing logs, and providing fixes, but does not clarify if the tool is read-only, what permissions are needed, or if any state changes occur. The JSON formatting instruction is a parameter constraint, not a behavioral disclosure.

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 concise with two main sentences and a critical usage note. It is front-loaded with the tool's purpose. The note about JSON formatting, while necessary, could be better integrated, but overall it is efficient.

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 complexity (4 parameters, no output schema, no annotations), the description is insufficient. It does not explain what the diagnostic output contains, how to interpret results, error handling, or how 'actionable fixes' are presented. The purpose is clear but the operational details are lacking.

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 coverage is 100% with clear descriptions for all four parameters (verbose, clientId, logLines, includeExecutions). The description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'Run comprehensive n8n diagnostics' and lists specific actions (container status, log analysis, fixes), providing a clear verb+resource. However, it does not distinguish from related siblings like n8n-analyze-logs or n8n-health-check.

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?

No guidance on when to use this tool versus alternatives. It does not specify prerequisites, contexts, or when not to use it. The note about JSON formatting is a parameter requirement, not usage guidance.

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