Create user

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

The description discloses meaningful behaviors beyond the annotations: omitted dataLimit and expire default to unlimited, and explicitly provided fields override template values. This helps agents predict side effects without contradicting the annotations.

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 compact, information-dense sentences with no wasted words. The most important defaults and template behavior are communicated without burying the core purpose.

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 the complex 10-parameter schema and rich nested properties, the description covers the key non-obvious behaviors and relies on the schema for remaining parameter details. The main gap is not mentioning that omitting proxies uses server defaults on create, though the schema covers this.

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 70% schema coverage, the description adds real interpretive value for dataLimit, expire, and templateId, including human-readable sizes, relative durations, absolute dates, and template override semantics. It does not cover every optional parameter, but the schema already documents most of them well.

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 uses a specific verb+resource — 'Creates a new user' — and is unambiguously distinct from sibling tools like marzban_users_update, marzban_users_get, and marzban_users_list. It also clarifies the tool's exact scope by not merely restating the title.

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 core purpose makes when-to-use obvious, but the description does not explicitly distinguish from alternatives or state when not to use it. It gives internal guidance around templateId and defaults, but no direct routing such as 'use update for existing users'.

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