n8n_manager_history

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it handles this well by explicitly stating 'Read-only' and explaining the critical failure mode when the environment variable is missing, including the consequence of talking to n8n directly. It could go further by describing response shape or pagination, but the two most operationally important behaviors are disclosed.

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?

Three sentences, all front-loaded with purpose first, then the critical precondition and failure mode, then the safety statement. Every sentence earns its place with distinct information and there is zero wasted text.

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 read-only, 2-parameter tool with fully self-documenting parameters, the description covers purpose, safety, and the key operational gotcha (environment variable). The main gap is the absence of an output schema combined with no description of the return structure, though naming the three content sections partially compensates by letting an agent infer the response shape.

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%; both parameters are already well-documented in the schema (limit range of 1-500, workflow_id disambiguation from n8n instance ID, and the omit-to-list behavior). The description adds only marginal context by naming the three history sections ('version history, recorded decisions, and sync history'), which loosely maps to what 'per history section' means, so the baseline 3 is appropriate.

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 specific verb ('Read') and a specific resource ('version history, recorded decisions, and sync history') from a 'running n8n-workflow-manager', which clearly distinguishes this tool from all siblings, none of which target manager history. The manager-vs-direct-n8n distinction further disambiguates it from tools like n8n_list_executions and n8n_list_backups.

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 provides an explicit precondition ('Requires the N8N_MCP_MANAGER_URL environment variable') and a clear when-not-to-use condition ('without it, this MCP talks to n8n directly and no such history exists'). This tells an agent when the tool will fail or return nothing. However, it does not name specific sibling alternatives for obtaining history from a direct n8n connection.

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