n8n-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions prerequisites but lacks details on what 'pull' entails (e.g., merges changes, updates local repo, potential conflicts), rate limits, error handling, or output format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized with two concise sentences that front-load key information: the action and prerequisites. There's no wasted text, and it efficiently communicates the essentials without unnecessary detail.

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 tool's complexity (a Git operation with prerequisites), no annotations, and an output schema present (which may cover return values), the description is somewhat complete but has gaps. It covers purpose and usage guidelines adequately but lacks parameter details and behavioral context, making it minimally viable but not fully comprehensive.

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 has 1 parameter ('force') with 0% description coverage, and the tool description doesn't mention any parameters. Since schema coverage is low (<50%), the description should compensate by explaining parameter meanings, but it adds no information beyond the schema. This leaves the 'force' parameter undocumented in both places.

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 states the verb ('pull') and resource ('changes from the connected Git repository'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from potential siblings like 'activate_workflow' or 'execute_workflow', which are unrelated but share the same server context, so it misses full sibling differentiation.

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 clear context for when to use the tool by stating prerequisites: 'Requires write_mode and source control configured.' This gives explicit guidance on necessary conditions. However, it doesn't mention when not to use it or name alternatives, such as other source control operations not listed in siblings, so it falls short of full explicit alternatives.

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