n8n-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, the description doesn't address important behavioral aspects: whether this requires specific permissions, what happens on duplicate table names, whether tables can be modified after creation, or what the response contains. The mention of column requirements is helpful but insufficient for a mutation tool.

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 extremely concise - just two sentences that directly address the core functionality and parameter requirements. Every word serves a purpose with no wasted text. It's front-loaded with the main purpose followed by essential parameter guidance.

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 creation tool with no annotations but with an output schema, the description covers the basic purpose and parameter structure adequately. However, it lacks important context about behavioral aspects, error conditions, and usage guidelines that would be expected for a mutation tool. The presence of an output schema reduces the need to describe return values, but other gaps remain.

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?

With 0% schema description coverage, the description adds significant value by explaining the 'columns' parameter structure: columns need 'name' and 'type' with specific allowed values (string/number/boolean/dateTime). This compensates well for the schema's lack of documentation, though it doesn't mention the 'name' parameter's purpose or constraints.

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 'Create' and resource 'new data table', making the purpose immediately understandable. It distinguishes this from sibling tools like 'get_data_table' or 'list_data_tables' by focusing on creation rather than retrieval. However, it doesn't explicitly differentiate from other creation tools like 'create_workflow' or 'create_tag' beyond the resource type.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when this tool is appropriate versus other data table operations, or any constraints on usage. With multiple sibling creation tools available, this lack of differentiation is a significant gap.

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