sf_create_user

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create', which implies a write operation, but does not mention side effects like user activation status, required permissions, or the presence of a 'confirm' parameter that might require confirmation before creation.

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?

The description is a single, concise sentence that is front-loaded with the action 'Create' and the resource 'Salesforce User record'. Every word contributes to the core message, with no redundancy or 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?

For a tool with 16 parameters, no output schema, and no annotations, this one-sentence description is severely under-specified. It fails to mention required fields, operational prerequisites, or any guidance on how the tool behaves, making it inadequate for an AI agent to correctly select and invoke the 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?

The description mentions 'profile and locale settings', which loosely maps to parameters like profileName, profileId, localeSidKey, etc. However, with 16 parameters and 0% schema description coverage, it does not explain the required fields (username, email, lastName, alias) or other essential parameters, leaving most parameters undefined.

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 Salesforce User record' with a specific verb and resource, distinguishing it from generic tools like sf_create_records. Referencing profile and locale settings further clarifies the tool's specific scope.

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 description provides no guidance on when to use this tool versus alternatives such as sf_create_records or sf_update_records. There is no mention of prerequisites, disambiguation, or scenarios where this tool is preferred.

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