n8n_get_instance_info

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

No annotations are provided, so the description carries full burden. While 'Get' implies read-only, the description doesn't explicitly confirm this is safe (no side effects), mention authentication requirements, or describe error behavior for invalid sites.

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 appropriately brief at one sentence, but the '[UNIFIED]' prefix appears to be implementation metadata that doesn't help the agent. The core message is front-loaded but omits critical parameter context.

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 only one required parameter and no output schema, the description should document the parameter. The lack of any parameter explanation creates a critical gap for a tool that cannot be invoked without knowing what 'site' refers to.

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 'site' parameter has 0% schema description coverage, and the description fails to compensate by explaining what 'site' means (URL, ID, name?) or providing an example. An agent cannot correctly invoke this tool without guessing the parameter format.

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 clearly states the tool retrieves 'n8n instance information' with specific examples (version and configuration), distinguishing it from sibling n8n_get_* tools that retrieve specific resources like workflows or users. The '[UNIFIED]' prefix is unnecessary metadata but doesn't obscure the purpose.

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 provided on when to use this versus alternatives like n8n_health_check or when instance information is needed versus specific resource details. No prerequisites or conditions are mentioned.

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