n8n_create_credential

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention idempotency (what happens if the credential name exists), security implications, required permissions, or what the tool returns upon success/failure. The '[UNIFIED]' prefix is opaque and adds no behavioral context.

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 compact at two sentences and front-loads the purpose. However, the '[UNIFIED]' prefix appears to be metadata noise that doesn't aid the agent. The second sentence provides actionable guidance without redundancy.

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 4 required parameters with 0% schema coverage, no annotations, and a nested object structure for 'data', the tool is moderately complex. The description is insufficiently complete—it delegates all parameter documentation to external tools without explaining the parameter relationships (e.g., how 'type' determines 'data' structure) or providing fallback documentation for simple parameters.

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 must compensate for 4 required parameters including a complex nested object ('data'). While it hints to use get_credential_schema for the 'data' field contents, it provides zero explanation for 'site' (instance URL?), 'name' (display name vs ID?), or 'type' (valid values?), leaving critical parameters undocumented.

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 'Create a new credential' with a specific verb and resource. However, it does not distinguish from sibling tools like n8n_transfer_credential (which may create copies) or clarify what constitutes a 'credential' in the n8n context.

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 one explicit workflow guideline: 'Use get_credential_schema to see required fields,' indicating a prerequisite step. However, it lacks guidance on when NOT to use this tool (e.g., when to use transfer instead), prerequisites for the 'site' parameter, or error handling scenarios.

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