n8n_get_node

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

Annotations already mark the tool as read-only, and the description adds meaningful detail about the output contents: parameter types, options, display conditions, credentials, latest typeVersion, and curated notes. This goes beyond the schema and annotations, helping the agent anticipate what will be returned.

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 dense sentence that front-loads the verb and object, then efficiently lists the return contents. Every phrase adds value and there is no filler.

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 read-only lookup with one required parameter and no output schema, the description provides enough detail about what the agent will receive. A minor gap is the lack of explicit behavior for unknown or uncommon node types, but that is not necessary for correct invocation.

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 covers the single parameter completely, including an example of valid aliases ('n8n-nodes-base.slack' or 'webhook'). The description does not add much beyond this, so the baseline 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 starts with a specific verb ('Get') and a precise resource ('real parameter schema of an n8n node type'). It enumerates exactly what the result includes: parameters, types, options, display conditions, required params, credentials, typeVersion, notes, and an example. This clearly differentiates it from siblings like n8n_get_credential_schema and n8n_search_nodes.

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 does not explicitly state when to use this tool versus alternatives. While the purpose is clear, there is no mention of when to prefer it over n8n_get_credential_schema or n8n_search_nodes, and no exclusions or prerequisites are provided.

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