How to use this server

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

No annotations are provided, so the description carries the full burden. It discloses that the tool provides a usage guide and that management features are conditional ('if configured'), informing the user about potential limitations. However, it doesn't explicitly state that the tool has no side effects or that it returns text/markdown, which would be helpful.

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, front-loaded sentence that immediately states 'Usage guide' then expands with specific topics and a call-to-action. No wasted words.

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 documentation tool with no parameters and no output schema, the description covers the key aspects: what it is, what topics it covers, and when to call it. It could mention the output format, but overall it's sufficient for a simple guide 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 tool takes zero parameters, so the schema is empty. The description doesn't need to explain parameters; the baseline of 4 applies.

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 opens with 'Usage guide', clearly identifying the tool's function as providing guidance. It enumerates covered topics (looking up nodes, validating configs, managing n8n instance) and distinguishes it from sibling tools by positioning it as the starting point ('Call this first').

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?

Explicitly states 'Call this first if unsure where to start', providing clear when-to-use guidance. The 'recommended workflow' phrasing implies this is the entry point for other operations, though it doesn't explicitly name alternatives.

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