n8n-login

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

No annotations provided, so description bears full burden. It discloses the return of a session cookie and the necessity for REST API operations. It does not cover error handling, rate limits, or credential storage safety.

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?

Two sentences, front-loaded with the action 'Login to n8n using email/password'. Every sentence adds value: purpose, output, and motivation.

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 login tool with no output schema, the description covers what it does, what it returns, and why it's needed. It lacks instructions on how to use the returned session cookie, but this is somewhat implied by the context of REST API operations.

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 each parameter described. The description does not add significant meaning beyond what the schema already provides (e.g., it just mentions email/password but not clientId details). Baseline of 3 for high coverage.

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 is for login using email/password and returns a session cookie. It distinguishes itself from all sibling tools (which are CRUD operations) by being an authentication prerequisite.

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 implies usage before other REST API tools (e.g., list-credentials) and mentions that some endpoints are not available in Public API, providing context. However, no explicit 'when not to use' or alternatives are given.

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