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

Annotations already declare this as a safe, read-only, closed-world operation, so the main disclosure burden is reduced. The description adds useful detail about return contents, including credentials and a ready-to-paste skeleton, but does not cover error behavior or lookup limitations.

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 front-loaded and efficient, giving the core return value first and then the accepted input forms. The Args section is slightly redundant but still useful for clarity.

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?

With no output schema, the description appropriately explains what the tool returns and what input formats are accepted. It is nearly complete, though it could mention behavior for unknown or ambiguous node names.

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 0%, so the description must explain the single parameter, and it does: catalog name, full type, or short type, with examples for each. This meaningfully compensates for the bare schema string.

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 a specific resource and what it returns: the full definition of one n8n node, including type/typeVersion, defaults, credentials, and skeleton. It is clear, but it does not explicitly distinguish itself from the sibling search_nodes tool.

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?

It implies the tool is for looking up one known node and lists accepted input formats, which helps. However, it does not state when to use this instead of search_nodes or what to do when the node is unknown.

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