nex_account_create

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

No annotations are provided, so the description carries the full burden. It does add useful behavior beyond the schema — credentials are optional and write-only, and the tool records a catalog entry rather than performing a login. It omits what happens on duplicate platformUrl, required permissions, and whether an identifier is returned, which matters for a mutation tool with zero annotation coverage.

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 front-loaded sentences: what it creates, what to pass, then the negative disambiguation. No filler, and the required parameter is named before the optional ones.

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?

There is no output schema and no annotations, and the description covers the creation target, the batch shape, the required field, credential write-only semantics, and one behavioral exclusion. The remaining gap — what identifier comes back — is minor given the schema already documents every field.

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 coverage is 75%, so the schema already documents platformUrl (with example), username, password and key2fa. The description reinforces the required/optional split and the write-only nature of secrets, but says nothing about teamId, remark, platformName, or how the flat parameters relate to the items array — leaving the parameter surface as documented by the schema alone.

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 platform account in the workspace catalog, with singleton-or-array semantics spelled out. It does not, however, differentiate itself from the closely named sibling nex_account_batch_create, which appears to do the same 'several at once' job — an agent has no textual basis for choosing between them.

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?

"This does not fill a login form" is a real when-not hint that steers away from nex_browser_fill_account / nex_browser_fill_credentials, but neither alternative is named. There is no guidance on when to use this versus nex_account_batch_create, nor any prerequisite (existing team, workspace, permissions).

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