init-n8n

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 establishes a connection, implying it's a setup or initialization operation, but lacks details on behavioral traits like error handling, authentication requirements beyond the API key, or whether it's idempotent. The description adds some context but doesn't fully compensate for the absence of annotations.

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 sized and front-loaded: the first sentence states the purpose, the second provides usage guidelines, and the third gives a critical formatting instruction. Every sentence adds value without redundancy, making it efficient and well-structured.

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 the tool's complexity (a connection initialization with 2 parameters), no annotations, no output schema, and low schema coverage, the description is somewhat complete but has gaps. It covers purpose and usage but lacks details on behavioral aspects, parameter meanings, and expected outcomes, making it adequate but not fully comprehensive for an initialization 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 input schema has 2 parameters with 0% description coverage, meaning the schema provides no semantic details. The description adds minimal parameter semantics by mentioning 'n8n URL and API key' and specifying a format requirement ('compact, single-line JSON without whitespace or newlines'), which helps clarify usage. However, it doesn't explain what the URL or API key represent or their expected formats, leaving gaps.

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's purpose: 'Initialize connection to n8n instance.' It specifies the verb ('Initialize') and resource ('connection to n8n instance'), making it unambiguous. However, it doesn't explicitly differentiate from siblings like 'create-credential' or 'create-project', which are distinct operations, so it doesn't reach the highest score.

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 provides clear context for when to use this tool: 'whenever an n8n URL and API key are shared to establish the connection.' This gives explicit guidance on the triggering condition. However, it doesn't mention when not to use it or name specific alternatives among the siblings, such as other initialization or setup tools, which prevents a perfect score.

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