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 'Requires write_mode', hinting at permission needs, but lacks details on critical traits like whether the operation is idempotent, how errors are handled (e.g., partial inserts), rate limits, or what happens on duplicate rows. 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 two sentences that are front-loaded with the core action and efficiently convey key details without waste. Every sentence adds value: the first defines the operation and data structure, the second notes a prerequisite. There's no redundancy or unnecessary elaboration, making it highly concise and well-structured.

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 write operation with 2 parameters), no annotations, and an output schema present (which reduces the need to describe return values), the description is minimally adequate. It covers the basic purpose and parameter hints but lacks behavioral context like error handling or permissions details. With output schema handling returns, it's complete enough for basic use but has gaps for robust agent operation.

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 0% description coverage, so the description must compensate. It adds meaning by explaining that 'rows' is an array where each row is a dict of column_name:value, clarifying the structure beyond the schema's generic 'object' type. However, it doesn't detail 'table_id' (e.g., format or source) or provide examples, leaving some parameters only partially explained. This meets the baseline for low schema coverage but doesn't fully compensate.

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 action ('Insert rows') and resource ('data table'), specifying that each row is a dict of column_name:value. It distinguishes from sibling tools like 'query_table_rows' (read) and 'create_data_table' (create table structure). However, it doesn't explicitly differentiate from potential overlapping tools like 'update_workflow' that might also modify data, making it a 4 rather than a 5.

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 some guidance by mentioning 'Requires write_mode', which implies a prerequisite or context for usage. However, it doesn't explicitly state when to use this tool versus alternatives like 'update_workflow' or 'create_data_table', nor does it specify exclusions or detailed scenarios. This leaves usage somewhat implied rather than fully explicit.

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