create-credential

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

With no annotations provided, the description carries full burden. It mentions the creation action but doesn't disclose behavioral traits like authentication requirements, rate limits, whether credentials are stored securely, or what happens on failure. It only provides procedural guidance about using get-credential-schema first.

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 sentences that are well-structured and front-loaded with the main purpose. The second sentence provides important procedural guidance. No wasted words, though it could be slightly more concise by integrating the examples more smoothly.

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-parameter creation tool with no annotations and no output schema, the description provides adequate purpose and usage guidance but lacks details about authentication requirements, error handling, and complete parameter documentation. It's minimally viable but has clear gaps in behavioral transparency and parameter semantics.

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%, so the description must compensate. It only mentions the 'type' parameter with examples and implies 'data' contains credential fields, but doesn't explain 'clientId' or 'name' parameters. The description adds some meaning for 'type' and 'data' but leaves 'clientId' and 'name' completely 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 the tool creates a credential for nodes of a specified type, with specific examples of credential types. It distinguishes from siblings like delete-credential and get-credential-schema by focusing on creation. However, it doesn't explicitly contrast with other creation tools like create-project or create-workflow.

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 explicit guidance on when to use this tool: after using get-credential-schema to see required fields. It also specifies the context (credential type names from n8n UI) and implies not to use it without first checking schema requirements.

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