create_user

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

Since no annotations are provided, the description is the sole source of behavioral info. It notes the tool is marked [DESTRUCTIVE] (though creation is not typically destructive), requires confirmation, and returns the created user with Id. Missing details on side effects, permissions, or reversibility.

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 with clear front-loading of the [DESTRUCTIVE] flag. Every word serves a purpose, no redundancy.

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 no output schema, the description mentions the return value. It covers prerequisite steps and confirmation. Lacks details on error conditions, rate limits, or authentication requirements, but is sufficient for a creation 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 coverage is 100% with descriptions for all parameters. The description only reiterates that Number must be unused, adding no new semantic value beyond the schema's own documentation.

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?

Clearly states that the tool creates a new 3CX user/extension, distinguishing it from sibling tools like update_user and delete_user. The verb 'Creates' directly matches the tool's function.

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?

Explicitly advises using find_users to check number availability before creation and mentions user confirmation is required. However, it does not specify when to avoid using this tool (e.g., if user already exists) or compare with alternatives like update_user.

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