n8n_remove_server

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

Without annotations, the description carries full burden. It does not disclose if removal is permanent, requires confirmation, or has side effects. No mention of permissions needed or behavior for non-existent server.

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?

Single sentence is concise and front-loaded. No wasted words. Could benefit from additional context but not at expense of brevity.

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 removal tool with one parameter, the description is too minimal. It lacks information on idempotency, error states, or relationship to sibling tools like n8n_add_server. Output schema is absent, but description should still hint at return value or confirmation.

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 100% with one required parameter 'server_name' with clear description. The description adds the context that removal is from configuration, but parameter insight is already complete in schema.

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 'Remove an n8n server from the configuration' clearly states the verb (remove) and resource (n8n server). However, it does not differentiate from sibling tools like n8n_delete_workflow, which is a different resource but similar verb. The description is clear but lacks specificity about the scope.

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 on when to use this tool vs alternatives (e.g., n8n_list_servers to see available servers, n8n_ping_server to check status). The description does not mention prerequisites (e.g., server must exist) or consequences (e.g., irreversible removal).

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