n8n_source_control_pull

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 but offers minimal detail beyond identifying the operation as a sync from a connected repository. It does not clarify whether the operation is destructive (overwriting local workflows), how Git conflicts are resolved, or what the return value 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 relatively brief at four sentences and front-loads the core action, but contains redundancy between 'Pull workflows...' and 'Syncs workflows...'. The inclusion of metadata tags '[UNIFIED] [Enterprise]' and the inaccurate parameter claim reduce overall information density.

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?

Given the complexity of Git-based synchronization operations and complete lack of schema documentation, the description is insufficient for safe invocation. It omits critical context such as conflict resolution behavior, the meaning of the 'force' flag, and the structure of the return value.

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 has 0% description coverage, leaving the description to compensate, yet it only provides the incorrect statement that 'All parameters are OPTIONAL.' It fails to explain that 'site' refers to the n8n instance identifier, what 'variables' controls, or the behavioral function of the 'force' parameter.

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 clearly identifies the specific action 'Pull workflows from source control (Git)' and resource (workflows), distinguishing it from sibling import/export tools by specifying the Git/repository context. The '[Enterprise]' tag further clarifies licensing scope. However, it does not explicitly contrast usage with similar siblings like n8n_import_workflow.

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 states the prerequisite 'Requires n8n Enterprise/Pro license' but fails to provide guidance on when to use this tool versus alternatives like n8n_import_workflow. Critically, it falsely claims 'All parameters are OPTIONAL' despite the schema marking 'site' as required, which could mislead agent invocation.

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