user_create

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

Discloses write nature and the preview/execute pattern via dry_run and confirm. Consistent with annotations (readOnlyHint false, destructiveHint false). No contradiction.

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, no waste. Purpose is front-loaded, behavior and usage are concisely stated.

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?

Adequate for a create tool with no output schema. Covers key behavioral aspects. Could mention uniqueness constraints but not essential.

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 has 100% coverage; description adds clarifying usage for dry_run and confirm parameters, helping the agent understand the safety pattern.

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 'Create a new FastPanel system user', using a specific verb and resource. It distinguishes from sibling tools like users_list, and no other tool creates users.

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 clear context: it's a WRITE operation with dry_run for preview and confirm for execution. However, it does not explicitly state when to use vs alternatives, though no direct alternative exists.

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