Create multiple platform accounts at once from an items array, each requiring a platform URL. Secrets like passwords and authenticator keys are write-only and never returned.
Create multiple platform accounts from an items array. Each item needs platformUrl. Secrets are write-only and never returned.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Account objects; each item needs platformUrl. Also accepts accounts or accountList |
Changes observed during successful MCP inspections.
v2026.10.24Input schema / properties / items / items / properties / password / descriptionPrevious value: -"Write-only; never returned"New value: +"Write-only"v2026.8.20Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that secrets are write-only and never returned, but it omits important mutation behavior such as permissions, atomicity, partial-failure handling, and rate limits.
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?
Three short sentences, front-loaded with the core operation, followed by the required input detail and the key secret-handling caveat. There is no filler.
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?
The schema is fully documented and the description covers the essential input requirement, but with no annotations and no output schema it should say more about batch results or failure behavior. It is minimally adequate rather than complete for a batch mutation tool.
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 100%, so the nested fields including platformUrl, username, password, key2fa, teamId, and platformName are already documented. The description adds little beyond repeating that each item needs platformUrl and that secrets are write-only.
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 multiple platform accounts'. The word 'multiple' distinguishes it from the single-account sibling nex_account_create, and the input shape is named directly as an items array.
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 batch nature implies when to use it, but the description does not explicitly compare it to nex_account_create, state prerequisites, or explain when not to use batch creation. Usage is inferable but not fully guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.