n8n_add_project_users

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

No annotations provided, so description carries full burden. Only behavioral disclosure is the license requirement. Missing: idempotency (what happens if user already in project?), safety profile, error conditions, or rate limits. 'Add' implies mutation but side effects aren't detailed.

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?

Extremely brief with two information-dense sentences. The leading '[UNIFIED] [Enterprise]' tags are metadata noise rather than descriptive content, but the core description is appropriately sized without redundancy. Every sentence earns its place, though more content was needed.

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?

Inadequate for a tool involving nested array parameters (users) and no output schema. Lacks explanation of return values, success/failure indicators, or what 'project' refers to in the n8n context. Given the complexity of user-role mapping operations, the description is insufficient for confident invocation.

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 has 0% description coverage for all three parameters (site, project_id, users). Description fails to compensate: doesn't explain what 'site' refers to (URL? name?), what the 'users' array structure should be (objects with role fields? user IDs?), or expected formats. Critical gap for the complex 'users' array parameter.

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 the specific action 'Add users to a project' and mentions 'with roles' to distinguish from simple user creation. Differentiates reasonably from siblings like 'n8n_remove_project_user' and 'n8n_create_user'. However, 'with roles' is slightly ambiguous regarding whether it assigns roles or references existing user roles.

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?

Provides prerequisite context with 'Requires n8n Enterprise/Pro license', indicating when the tool is available. However, lacks guidance on when to use this versus 'n8n_change_project_user_role' for existing project members, and doesn't mention idempotency or error cases.

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