n8n_add_user_to_project

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 only says 'Add a user to a project with a specific role' and does not disclose what happens if the user already belongs to the project, whether roles are overwritten, whether it is idempotent, or what the response contains.

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 a single focused sentence with no filler. It leads with the action and includes the essential qualifier about roles.

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?

The operation is simple and all three required parameters are documented in the schema. However, with no annotations, no output schema, and no mention of valid role values or edge-case behavior, the description is only minimally viable for correct 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 description coverage is 100%, so each parameter already has a basic description. The tool description adds no meaningful parameter semantics beyond 'specific role', and valid role values are not specified even though there are no enums.

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 states a clear action ('Add a user to a project') and a key qualifier ('with a specific role'). This distinguishes it from remove/change operations at a basic level, though it does not explicitly contrast with sibling tools like n8n_change_user_project_role.

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?

There is no guidance on when to use this tool versus n8n_change_user_project_role or n8n_remove_user_from_project. The description implies the use case but gives no exclusions, prerequisites, or alternative routing.

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