n8n_set_safety_mode

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the setting names. It does not mention side effects such as read_only blocking operations across tools, backup_before_mutations triggering exports, or audit_log appending to a file. Some of this appears in parameter descriptions, but the main description adds no behavioral context.

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 well-structured sentence with a colon-led list that front-loads the tool's purpose. Every word earns its place and there is no filler or repetition.

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 low-complexity tool with three optional booleans and full schema descriptions, the description plus schema is largely sufficient. The only notable gap is that the description does not state whether the settings persist or apply globally to all subsequent tool calls, but the parameter descriptions compensate for most practical ambiguity.

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% and each boolean parameter already has a meaningful description explaining its effect, so the baseline is 3. The description merely lists the parameter topics without adding default values, interactions, or invocation-level detail.

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 uses a specific verb ('Configure') and a clear resource ('local safety settings'), and enumerates the three settings: read-only mode, backup-before-mutation, and audit logging. The tool name also distinguishes it from the sibling n8n_safety_status, though the description does not explicitly contrast them.

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 is provided about when to use this tool versus n8n_safety_status or other siblings. There are no prerequisites, exclusions, or conditions such as 'use this before running mutations' or 'check n8n_safety_status to view current settings'.

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