n8n: Get instance info

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description's burden is lower. The description adds that returned data covers version and configuration, but says nothing about authentication requirements, per-site connectivity assumptions, latency, or error behavior when a site is unreachable.

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?

A single front-loaded sentence with no wasted clauses. The '[UNIFIED]' prefix is unexplained metadata that adds no meaning for an agent, which keeps it from a 5.

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 getter with no output schema, the description covers the broad shape of the return (version, configuration) but leaves the required 'site' input and the instance-selection behavior entirely undocumented. It is adequate to identify the tool but thin for calling it correctly.

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 sole parameter 'site' has 0% schema description coverage, and the description never explains what a site value looks like (URL, slug, alias?) or that it selects which n8n instance to query. With full burden on the description for the only required input, this is a clear gap.

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 ('Get') and resource ('n8n instance information'), and narrows scope to version and configuration, which separates it from workflow/credential/user getters in the sibling list. It does not explicitly contrast with the other '*_get_instance_info' siblings, so it stops short of a 5.

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?

There is no guidance on when to call this versus alternatives such as get_system_info or get_project_info, and no stated preconditions or exclusions. An agent must infer the use case from the name alone.

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