n8n: Create credential

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

Annotations already tell the agent this is a non-read-only, non-idempotent, non-destructive write. The description adds nothing beyond that: no mention of required API permissions, whether duplicate names are rejected, whether creation is validated against the type, or what happens on partial failure — a notable gap for a mutation that accepts a free-form data blob.

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?

Two short, front-loaded sentences with zero filler; the action is stated first and the prerequisite second. It is efficient, though efficiency here comes at the cost of the missing details scored elsewhere.

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 4-required-parameter mutation with a nested open-ended object and no output schema, the description is thin: it never says what the call returns, what 'site' refers to, or what shape 'data' must take beyond pointing at another tool. The redirect to get_credential_schema is the only thing making it callable.

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?

Schema description coverage is 0% for four required parameters including a free-form nested 'data' object, so the schema alone gives almost no meaning. The description partially compensates by delegating to get_credential_schema, but still does not explain 'site', 'type', or how 'data' relates to the requested schema.

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?

States a specific verb and resource ('Create a new credential'), which cleanly separates it from the get/delete/transfer credential siblings. The '[UNIFIED]' prefix adds no discriminating information, and no scope details (per-site scoping, credential types) are given.

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?

Provides one concrete workflow instruction: call get_credential_schema to learn required fields, which is genuinely useful sequencing. It does not say when to prefer this over siblings or what prerequisites/permissions are needed to create a credential on a given site.

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