n8n_safety_status

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

With no annotations, the description carries the full burden and does well: 'Show' communicates non-mutating behavior, and it further discloses that the tool checks whether the optional n8n-workflow-manager seam is configured and reachable. It also states exactly what data will be returned, so an agent can expect a safe inspection call.

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, front-loaded sentence that names the resource first and then lists the specific scopes covered. There is no repetition, filler, or unnecessary information.

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 zero-parameter status tool with no output schema, the description is complete: it identifies the operation, the resource, and every category of information the tool reports. An agent has enough to invoke it correctly and understand what it will return.

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 input schema is empty, with zero parameters, so there is no parameter ambiguity to resolve. The 0-parameter baseline applies, and the description adds no parameter details because none are needed.

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 the verb 'Show' with a specific resource and enumerates the exact content: safety settings, backup directory, audit log location, and seam status. This clearly differentiates it from mutating siblings like n8n_set_safety_mode and from history/backup-listing 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?

The description gives clear context for a read-only status inspection: use it when you need the current safety settings, backup directory, audit log location, or seam reachability status. It does not explicitly name alternatives or exclusions, but the 'Show' framing contrasts naturally with the mutating n8n_set_safety_mode sibling.

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