n8n_update_project

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only says 'Update a project.' It does not state whether the update is partial, whether omitted fields are reset, 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 one short sentence with no filler, but it is under-specified rather than appropriately concise. It repeats the tool name's meaning without providing any additional useful structure.

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 mutation tool with no annotations and no output schema, the description is not complete enough. The schema supplies the parameters, but the agent still lacks context about update semantics, return value, and when to prefer this tool over sibling project tools.

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 schema already documents id and name, and the type enum is reasonably self-explanatory, but the description adds no parameter-level meaning. It does not clarify whether type changes are allowed or how omitted parameters affect the project.

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 'Update a project.' is a direct restatement of the tool name and adds no detail about what is actually updatable. It provides a verb and resource, but does not distinguish updating project attributes from related project membership or role update tools.

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 about when to use this tool versus creating, deleting, or managing project membership. It also does not mention prerequisites such as the project needing to exist before an update.

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